Post

Cam McHenry
@camchenry.com

It's a convention in oxlint. When it's a ported rule, we normally call the rule origin by what the plugin was called. In this case the rule originated from typescript-eslint even though it's implemented in Go.

Mike Greiling
@mike.greiling.me

I understand the eagerness to get a performant type checker plugged into oxlint, but tsgo is not even stable yet, is it? seems premature to build tsgolint before typescript 7 is even in alpha

Alexander Lichter
@thealexlichter.com

tsgo supported most type-checking rules already in May when the native preview was announced! Also, oxlint with type-aware linting is still considered experimental, but our tests in different repos were successful. As usual, if there are any problems, let us know via issue or Discord!

devblogs.microsoft.comAnnouncing TypeScript Native Previews - TypeScriptPreviews of the native TypeScript port are now available on npm and for VS Code through the Visual Studio Marketplace!
tent10.bsky.social
@tent10.bsky.social

Premature as in they’re signing themselves up for too much work? Or what’s the issue? It’s a very annoying problem that forces everyone to stay on eslint I think it’s very smart to get this going sooner than later

Mike Greiling
@mike.greiling.me

Yeah, generally speaking, writing a wrapper on top of another project which is in a pre-alpha state is just signing up for some headaches when unstable APIs you rely on change without notice. It's not that it cannot be done, it's just a lot more work to keep up with the upstream changes.