Closing TS 6.0 LS issues

[RyanCavanaugh]

Acknowledgement

• I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment

As discussed in our December blog post, we're in the process of closing all bugs related to the JavaScript implementation (AKA Strada AKA TypeScript versions 1.1 through 6.0) of the language service.

Why?

A very large part of the language service has basically been rewritten from scratch:

• We now use LSP instead of a custom protocol
• A large amount of logic was not directly portable, so got hand-authored instead, thus likely has a different set of problems

It's extremely time-consuming (and low-yield) to try to verify these issues, so instead we're taking a more blunt approach and instead doing a one-time bulk close of these issues.

In a future step, we'll also be applying this to PRs that change language service behavior, as all future development efforts should be invested in the native codebase. It's important that 6.0 remain a stable release and merging these PRs would potentially introduce servicing costs that would be better spent on the 7.0 codebase.

Why not tsc bugs too?

The port of the core checker logic is extremely faithful to the existing codebase, so almost every checking bug in TS is still present in the Go version (for better or worse!). We're trying to apply some more aggressive auto-verification of old bugs just to keep things tidy, but auto-closing checker bugs right now would discard too many valid issues.

When?

Now-ish, subject to GitHub API rate limits 🙂

What (should you do about it)?

Please try out your scenario in the TypeScript Native Nightly extension.

Three cases to consider:

• The feature isn't implemented yet, wait and try again later
• If the bug is fixed, no action is needed
• If the bug is still present, please log a new issue in the native repo so we can investigate

Happy coding!