Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/typescript-eslint/typescript-eslint/issues/10940 below:

Enhancement: Use TypeScript's Go port (tsgo

• I have searched for related issues and found none that match my proposal.
• I have searched the current rule list and found no rules that match my proposal.
• I have read the FAQ and my problem is not listed.

typescript-estree

• I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

TypeScript is getting ported to Go! It's going to be 10x faster! Blazing fast! Speed! 🔥 ⚡

https://devblogs.microsoft.com/typescript/typescript-native-port/

If we could use this to power typed linting, that'd be great for users. Type checking performance is the bottleneck for the vast majority of correctly configured lint rules that use typescript-eslint.

We believe there are currently at least three major difficulties with typescript-eslint using tsgo in 2025:

1. ESLint does not yet support asynchronous parsers: Change Request: allow asynchronous parser eslint/eslint#15475
   • It's very likely that tsgo will be consumed via native binding APIs (WASM), and so will almost certainly be asynchronous
   • typescript-eslint could in theory use something like synckit but that presents data serialization difficulties
   • Edit: per Enhancement: Use TypeScript's Go port (tsgo / typescript-go) for type information #10940 (comment) and Enhancement: Use TypeScript's Go port (tsgo / typescript-go) for type information #10940 (comment), this might not be a blocker for long (thanks @jakebailey and @nicolo-ribaudo for the notes!)
2. tsgo is not stable and is many months away from being stable. It won't likely be the primary stable version of TypeScript within the next ~1-2 major versions of typescript-eslint.
3. ESLint rules in and out of typescript-eslint still rely on the JS-land AST, so even if we had a stable async parser, there's design work to be done communicating AST nodes and type information back from Go/WASM land to JS-land

So, although we'd very much like to be 10x faster (!!), it will take a lot of design exploration and work.

If you'd like to work on this, please go ahead. Seeing your experimentation will help inform how typescript-eslint can adopt faster typed linting in the future. 🚀

If you're coming here because your typed linting is slow, please go through our typed linting performance troubleshooting guide: https://typescript-eslint.io/troubleshooting/typed-linting/performance. Properly configured linting should not be significantly slower than type checking.

💖

kirkwaiblinger, ronami, schoero, azat-io, MARCROCK22 and 35 moremaxmilton, TkDodo, HyperLife1119, SagnikPradhan, lcswillems and 1 moreronami, johnnyreilly, azat-io, MARCROCK22, marcagba and 15 more

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4