Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

typescript-language-server does not work with @typescript/typescript6

Open Beginner friendly
#64,094 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
tooling

Research direction

Start in the @typescript/typescript6 compatibility package's lib directory and compare the existing tsc.js wrapper with the missing tsserver.js entry point. Add the corresponding tsserver.js compatibility entry point and verify that typescript-language-server starts with the package.

Written by the indexing model from the issue text.

Description

🔎 Search Terms

lsp language server tsserver.js

🕗 Version & Regression Information
  • This is an issue with the new @typescript/typescript6 package
⏯ Playground Link

No response

💻 Code

No response

🙁 Actual behavior

I have installed both TypeScript 6 and 7 side to side following the blog post.
Unfortunately, typescript-language-server (which is a LSP wrapper around tsserver from TypeScript 6) does not work in this setup. It is looking for a tsserver.js file in node_modules/typescript/lib, which does not exist in @typescript/typescript6.

🙂 Expected behavior

The @typescript/typescript6 package is for compatibility with software based on TypeScript 6, so it should include a tsserver.js executable. I believe the only thing needed is to add a tsserver.js file in the lib directory containing:

require("@typescript/old/lib/tsserver.js");

(same pattern as the existing tsc.js file)
I tested it and typescript-language-server does start when adding this file.

Additional information about the issue

I know that TypeScript 7 includes a new native LSP server, but it does not have all the features that tsserver had. In particular the lack of code actions like "Move to file" make it so that I want to be able to switch between the old and the new server until the new server reaches feature parity.

Dominant language
Go
Stars
111k
Forks
14.4k
Avg merge
1d 15h
Merged PRs (30d)
115

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/TypeScript

All issues in microsoft/TypeScript

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.