-
Notifications
You must be signed in to change notification settings - Fork 201
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
Update to eslint v9 #2489
Update to eslint v9 #2489
Conversation
I have an alternative using |
No preference on my side, so whichever sounds best to you. |
Switch to using `deno` as that allows referring to the config packages without having to setup a `package.json` and other stuff required when running `eslint` through `node` now.
My preference is this approach with deno, it avoids having to manage the whole |
@Nemo157 @GuillaumeGomez I'm not sure I fully follow, is anything missing here? Or is this ready to be merged? Generally you two can merge too :) |
I prefer to let PR owners with merge rights to merge their own PRs once approved so it's waiting on @Nemo157 here. ;) |
Let's merge it then. |
Switch to using
deno
as that allows referring to the config packages without having to setup apackage.json
and other stuff required when runningeslint
throughnode
now.