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

Use Biome or Oxc instead of Eslint #10794

Open
NolwennD opened this issue Sep 8, 2024 · 4 comments
Open

Use Biome or Oxc instead of Eslint #10794

NolwennD opened this issue Sep 8, 2024 · 4 comments

Comments

@NolwennD
Copy link
Contributor

NolwennD commented Sep 8, 2024

Eslint v9 migration is painfull, Biome and Oxc offer an alternative to Eslint. Maybe it’s time to use one of them or both instead of Eslint.

Moreover, Biome is an alternative to prettier (with same rules) for typescript. Oxc have also is own prettier implementation in progress.

@fabienpuissant
Copy link
Collaborator

It look's great I didn't know these tools 😊

@NolwennD
Copy link
Contributor Author

Some explanations about aim and roadmap of Biome and Oxc
biomejs/biome#1281

@pascalgrimaud
Copy link
Member

Just wonder if we can keep both: eslint and biomejs/oxc, it means 2 init modules, with similar rules, so no conflict:

  • init
  • init-biomejs

I know it was a pain to migrate to eslint v9 but today it's still really popular

We need to study what is better.
Let's discuss :-)

@murdos
Copy link
Contributor

murdos commented Sep 20, 2024

Actually it's a bit more complex: eslint is setup in the typescript module, and is then patched by the Vue and react modules.
Angular is currently doing its own setup independently.

I agree that we should keep eslint, which is the current standard.

But we could have a new module that remove eslint and setup biome.

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

No branches or pull requests

4 participants