codesandbox / codesandbox/codesandbox-client
TypeScript LSP crash multiple times
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
The TypeScript LSP crash multiple times when using the IDE.
How has this issue affected you? What are you trying to accomplish?
- Because the TypeScript LSP crash so I need to open up the command palette (Super + K). Then choose the '> Instance: Restart TypeScript language server' options to restart the TypeScript LSP.
- Show the old error even it was fixed.
- No static type-checking and autocomplete.
- No autocomplete for imports.
- No error checking.
- Old errors keep showing even it was fixed.
To Reproduce
- Create new Devbox (Node.js template).
- Modify .devcontainer/(Dockerfile & devcontainer.json) to install pnpm and Nx CLI.
- Create a new Nx workspace (Angular standalone template).
- Add SSR to the app.
- Install Angular Material.
- Write Angular code.
- Sometimes TypeScript LSP crash (Show the old code error than crash before fixed).
Link to sandbox: link (optional)
My Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | 0.0.152 |
| Browser | Chrome 115.0.132, 120.0.6099.193 |
| Operating System | Windows 7, Android 12 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the crash using the Node.js Devbox, the .devcontainer/Dockerfile and .devcontainer/devcontainer.json changes, and the Angular SSR and Material setup described. Start from the “Instance: Restart TypeScript language server” command and compare the LSP state before and after a crash. Done means the crash and stale diagnostics are reproducible and the affected entry point is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, node.js, typescript
- Domain
- developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100