-
Notifications
You must be signed in to change notification settings - Fork 12.8k
The Typescript language service died unexpectedly 5 times in the last 5 Minutes #6726
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can you post a file that causes this problem? |
Hi, RyanCavanaugh! |
@khanyuriy we need some repro steps to be able to diagnose the issue. What version of vscode are u using? What version of TS? Do you have a custom tssdk? What are your compiler options? Can you build this project on the commandline? Does it reproduce on any file outside ur project? |
hi, mhegazy!
Version 0.10.6
Version 1.0.3.0
no, i haven't
{
yes, i build it with gulp-tsc
yes i have all js file compiled successfully |
can you share a project that reproduces the issue. i can not get it to reproduce with the information supplied. |
mhegazy, |
Add "node_modules" to the "excludes" option (see https://github.com/billti/ng2demo/blob/master/tsconfig.json#L10 as an example). |
hi, billti! |
#6670 should add node_modules to the excludes by default, so should handle this issue. |
Hello, I have the same error message from vscode, but I know where my problem comes from: Do you have a workaround to make tsserver working with virtualbox shared folders (something like polling maybe) ? Thank you in advance for your answers. |
@zhengbli, any ideas here? |
It seems that virtualbox shared folder didn't implement the underlying file change notification mechanism that the non-polling |
@zhengbli Can you open a new issue to track this and assign to yourself (if you haven't already). thanks. |
FYI: I repro this issue with the same set up, and running
Calling |
Hi, something is killing this service, after upgrading node to 5.5.
I have got this message "The Typescript language service died unexpectedly 5 times in the last 5 Minutes. Please consider to open a bug report"
Any suggest ?
The text was updated successfully, but these errors were encountered: