chore(maintenance): add biome to the project #2791
Merged
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.
Summary
Changes
This PR introduces
@biomejs/biome
as development dependency to the project as well as a newbiome.json
file that holds the configuration for the tool.The configuration used for Biome is roughly equivalent with the
eslint
/prettier
one that we are already using, except a couple notable differences:type
usage when importing a typeThere might be other subtle differences due to Biome being stricter and/or more opinionated than the tools we are already using. We'll refactor the code to use these new conventions as we migrate to the tool.
This is the first of a series of PRs (~10) that will off board each one of the packages in this repo from
eslint
/prettier
to Biome. Once this work is complete we'll be able to remove about 10 direct dependencies; this will lessen our maintenance burden in maintaining them up to date.As part of this PR I have migrated the
examples/app
workspace to use Biome. The changes for this project are minimal.Issue number: #2790
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.