Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request to move from ESLint + Prettier to BiomeJS for a unified formatting and linting approach #30

Open
AiSirachcha21 opened this issue Jun 2, 2024 · 1 comment

Comments

@AiSirachcha21
Copy link

AiSirachcha21 commented Jun 2, 2024

I know the project isn't a huge thing but that doesn't mean it can't stand to benefit from a few nice to haves.

Problem

Maintaining and dealing with multiple configurations for ESLint and Prettier tends to be tedious and time consuming despite the wide popularity of the 2 tools.

As complexity and the project size grows, there are well known reports that ESLInt and especially Prettier tend to slow down as more files need to be considered during the linting and formatting process. This is a well known issue and is a major reason why a lot of bigger applications tend to have the auto formatting turned off.

Additionally, having to install multiple packages to add on to ESLint's default configuration tends to be a pain to manage especially when rules need to be updated.

Solution

In my experience using Biome so far, it's streamlined a lot of this for me. 1 package for most things ESLint does and a formatter and linter in the same tool. Adding on to this the tool is light, fast and extremely easy to setup with an emphasis on a great developer experience when working with it.

An extension for biome exists on VSCode (as biomejs.biome) and is a great and light companion.

A full breakdown on the ESLint + Prettier comparison to Biome's configuration can be seen at

https://biomejs.dev/linter/rules/

@AiSirachcha21
Copy link
Author

I'm willing (and already have a branch created that will set this in place)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant