chore: migrate prettier & ESlint to Biome #842
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
|
|
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.
This PR requires some work, but I highly recommend considering the implications beforehand - I'm happy to bring it over the finish line if you're interested.
In my last few projects I've been using @biomejs/biome as a replacement for both Prettier as well as ESLint. It's a single and a lot faster than Prettier/ESLint.
There are noteworthy (web3 related) projects using @biomejs/biome already, like viem & wagmi.
If you're interested, there are a few steps to take. Mainly:
As this results in a ton of changes, discussing the changes in this PR first before actually running the format/lint scripts made most sense to me. Let me know what you think.