browser
Here are 4,779 public repositories matching this topic...
I'm making a client-side code editor with rudimentary Git support, and syntax highlighting for diff/patch files would be really nice - a way to view the whole diff in a single window (alternative to existing diffeditor - with similar colors to git diff console coloring), maybe would be useful for others too.
https://github.com/microsoft/monaco-languages/ asks to create issues in this repo...
-
Updated
Jun 1, 2022 - JavaScript
-
Updated
Jun 8, 2022 - TypeScript
-
Updated
May 22, 2022 - JavaScript
-
Updated
Apr 28, 2022 - JavaScript
-
Updated
Jun 2, 2022 - TypeScript
-
Updated
May 18, 2022 - Go
-
Updated
Mar 28, 2022 - JavaScript
-
Updated
Jun 8, 2022 - TypeScript
-
Updated
May 7, 2022 - TypeScript
Would it be possible to let folks pass their own slugify function to generate slugs for markdown headings? Some usecases for this are
- backward compatibility (if I'm migrating from some other framework)
- customization of slugs (one off custom transformations)
- handling special usecases for non-latin languages (like Urdu)
Possible alternative
If it is too much, [@sindresorhus/sl
-
Updated
Jun 8, 2022 - JavaScript
-
Updated
Jun 8, 2022 - TypeScript
-
Updated
Jun 8, 2022 - JavaScript
-
Updated
May 7, 2022 - TypeScript
-
Updated
May 16, 2022 - TypeScript
-
Updated
Jun 7, 2022 - JavaScript
-
Updated
Apr 11, 2019 - JavaScript
-
Updated
Jun 7, 2022 - Python
-
Updated
Jun 8, 2022 - Common Lisp
-
Updated
Aug 12, 2021 - JavaScript
The clone command currently requires the url parameter to be a URL of the remote repository. However, canonical git allows for local paths to be used when cloning a repository. This becomes an issue when attempting to clone a local-only repository, or using the ref parameter to specify a local-only branch for checkout during cloning.
Improve this page
Add a description, image, and links to the browser topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the browser topic, visit your repo's landing page and select "manage topics."


Verify canary release
Provide environment information
What browser are you using? (if relevant)
How are you deploying your application? (if relevant)
Describe the Bug
Linting throws a warning of
@next/next/no-img-elementwhen an<img>tag is inside a<picture>tag.<Image>