[AssetMapper] Add FAQ for code lint/format #19893
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Kocal
force-pushed
the
asset-mapper/format-and-lint
branch
from
d1e5918
to
d3b1bd5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi everyone,
Little self-promotional PR for AssetMapper, to indicates how users can lint and format their front assets when using the fresh
kocal/biome-js-bundle.It's a bundle around Biome.js, a (much) faster linter (than ESLint) and formatter (than Prettier), which does not requires any configuration to handle JS/TS, JSX/TSX, CSS files... and soon Vue/Svelte files.
Thanks!