21–30 of 49 posts
Earlier quoted context omitted.
Check biome or oxlint. I don't think any of them support all the rules of eslint
I've been using biome since it was called rome. It's an excellent formatter / linter and reduces the configuration down to a single npm install and a single json file. I highly recommend people try it out and ditch the configuration nightmare that is eslint.
Earlier quoted context omitted.
Err... isn't the whole point of a big number release to introduce big, breaking changes? All major projects have breaking changes... but only the nice ones do us the courtesy of saving breaking changes for major release milestones
> Err... isn't the whole point of a big number release to introduce big, breaking changes? Certainly not. Breaking changes should still be avoided as much as possible.
oh dear god, have mercy, how do i migrate to the new flat configuration format?
any ES linter written in rust?
Earlier quoted context omitted.
> Err... isn't the whole point of a big number release to introduce big, breaking changes? Certainly not. Breaking changes should still be avoided as much as possible.
So are you saying that now was not the time for a major release? Or are you saying that the major release had too many breaking changes?
I've started using https://biomejs.dev/ which is written in Rust. It's super fast compared to ESLint and doesn't require a ton of plugins to work (you just install the one @biomejs/biome package and that's it). The configuration is dead simple as well and it has VS Code and intelliJ support too. It also does formatting / prettifying in the same package as well. One downside though is it does not have support for Stan…
It makes those linters virtually impossible for many projects to adopt.
Seems like it's part of some larger anti composable tools trend that I really don't understand.
I've started using https://biomejs.dev/ which is written in Rust. It's super fast compared to ESLint and doesn't require a ton of plugins to work (you just install the one @biomejs/biome package and that's it). The configuration is dead simple as well and it has VS Code and intelliJ support too. It also does formatting / prettifying in the same package as well. One downside though is it does not have support for Stan…
Projects like Biome and oxc seem to focus so much on reimplementing rules from eslint and broader eslint ecosystem vs. creating a plugin system for custom rules. It makes those linters virtually impossible for many projects to adopt. Seems like it's part of some larger anti composable tools trend that I really don't understand.
I tried to migrate a few nights ago but gave up for now as it was too many changes. I will give it another go this week on a full stomach.