Repository navigation
[FEATURE]: Force LSP usage #8712
Description
Feature hasn't been suggested before.
- I have verified this feature I'm about to request hasn't been suggested before.
Describe the enhancement you want to request
Currently, some LSPs are auto-activated based on the project layout.
For instance, TS LSP is activated it seems if there is a package.json at the root of the repo with a typescript dependency, and a node_modules folder.
In my case, I'm working in a monorepo where the typescript workspace is one level lower. Would it possible to force-activate via config the use of the TS LSP (even if it means I need to put it in the PATH myself).
Reacted by Guillaume Bogard, Alexandru Ion, Tony, bartek1470, Simon Sölder, Taylor Steele, Marius Pocevičius, Eray Dereagzi, Tim Petricola, OverHash and 3 more
Activity
github-actions commentedon Mar 26, 2026
To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
OverHash commentedon Mar 26, 2026
{ "$schema": "https://opencode.ai/config.json", "lsp": { "typescript": { "command": ["pnpm", "dlx", "typescript-language-server", "--stdio"], "initialization": { "tsserver": { "path": "./client/node_modules/typescript/lib/tsserver.js", "fallbackPath": "./server/node_modules/typescript/lib/tsserver.js" } } } } }This config worked for me!