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

Support oxlint please #2047

Open
zayfen opened this issue Dec 23, 2023 · 2 comments
Open

Support oxlint please #2047

zayfen opened this issue Dec 23, 2023 · 2 comments

Comments

@zayfen
Copy link

zayfen commented Dec 23, 2023

Oxlint is more than 50 times faster than ESLint, please support oxlint.

@bbatsov
Copy link
Contributor

bbatsov commented Feb 28, 2024

Adding new checkers is very easy (see https://www.flycheck.org/en/latest/developer/developing.html#adding-a-syntax-checker-to-flycheck). PR, welcome!

@samvidmistry
Copy link

I looked into it a bit back and it doesn't seem like beginner friendly to me (I am a complete newbie so I could be wrong). Given that oxlint is written in rust, it has beautiful error messages that are going to be a nightmare to parse. My cursory look didn't give me any flag that we can pass to get errors in json format, like flycheck does with rust. Their own solution for VSCode uses a language server crate that they wrote.

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

3 participants