Update to eslint v9
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.
I have an alternative using node with a package.json instead if anyone has opinions on which to use: https://github.com/Nemo157/docs.rs/commit/2f41680fd1e02274252ab0450d687e43cbea6dc8
I have an alternative using
nodewith apackage.jsoninstead if anyone has opinions on which to use: Nemo157@2f41680
No preference on my side, so whichever sounds best to you.
My preference is this approach with deno, it avoids having to manage the whole package-lock.json when we don't really care about the transitive deps.
@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. ;)