[lelandfe]

e: ahhh frick this is just stupid AI spam for this dude’s project.

Supports… some ESLint rules. It is not “easy” to add support to Oxlint for the rules it does not.

The projects at my work that “switched” to it now use both Eslint and Oxlint. It sucks, but at least a subset of errors are caught much faster.

[dcre]

Vite+ is not “this dude’s project”, it’s made by the team that makes all the tools discussed in this article.

[TheAlexLichter]

Yeah, no. Real human here.

Oxlint does support core rules out of the box but has support for JS plugins[0] as mentioned. If you don't rely on a custom parser (so svelte or vue component for example) things just work. Even react compiler rules[1].

[0] https://oxc.rs/docs/guide/usage/linter/js-plugins.html [1] https://github.com/TheAlexLichter/oxlint-react-compiler-rule...

[lelandfe]

Definitely read AI tonality into the earlier comment, noticed it didn't call out your relationship to it, then saw that you had a comment history plugging it, and made assumptions.

My apologies. I'll follow through to the links next time.

[conartist6]

So as long as you only need the pre-installed software it's a great device eh. I'm the PC to your game console here. Parser extension? Piece of cake for us. Heck just to showboat we actually extended our es6 parser from our es3 parser, and then implemented each later standard as an extension of the earlier one. We're able to run parsers for pretty much any programming language, and making them super easy to write. We can do cross-language transforms with ease. We can be our own system of version control! We're going to be a real threat to GitHub. VoidZero is not even trying to do this stuff. Your vision is just so... small.

[TheAlexLichter]

As said in another comment: Curious to see what you are coming up! Talk is cheap