3 ms·
I know I'm being a bit negative with regards to ESLint, but I'd just go with BiomeJS these days. It's faster and more sensible with its default lints. And to b
by spoiler 2y ago
I know I'm being a bit negative with regards to ESLint, but I'd just go with BiomeJS these days. It's faster and more sensible with its default lints.
And to boot it comes with a very sensible (and Prettier compatible) formatter!
- jerrygoyal 2y agowish if it could support eslint plugins
- hoffs 2y agoIronic
- morbicer 2y agoWhy? Rspack supports webpack plugins even tho it's written in Rust. That's how you win at adoption. If Biome would support plugins the answer to post title "What's coming next for ESLint" will be "slide to obsolescence". Without it ESLint is going to cling on legacy codebases for a bit longer.
- spoiler 2y agoWhich lints are you missing?
- floydnoel 2y agoI've been looking into Biome as ESLint can't parse the 'with' keyword from TC39 (import attributes) which is supported in Node for a while now. No combination of plugins, ignores, or configurations can help because ESLint can't parse the file at all. Best I could do was disable ESLint for those files. I found Biome when looking at solutions, but i hadn't heard of anyone using or recommending it. I'll take a look and see if we can replace ESLint to handle that issue. Thanks!