-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
NPM Install fails when tsconfig is present in VSCode workspace #16955
Comments
Here's the start of the tsserver log in these cases:
|
@rbuckton / @andy-ms can you please take a look at this issue. I believe the root cause is a change we made in VSCode 1.13 that opens We're seeing fair number of people report this problem: microsoft/vscode#28593 I'll see if I can get a workaround in for vscode 1.14 |
This is because the configaFileDiagnostics is sent irrespective of what we decide to do with the file. Which ends up sending event to vscode about the that's in the staged directory)(that file may or may not end up being part of the project).. Look at https://github.com/Microsoft/TypeScript/blob/master/src/server/editorServices.ts#L649 Since vscode opens the trigger file, it would end up opening that file and that means we will watch the whole ancestor chain for addition of the tsconfig file. There are two issues here:
This would be updated with the changes I am making of which first batch will go out this Monday. |
@sheetalkamat: Any update on this? I'm still having trouble with VSCode 1.14.2. NPM works OK before I start VSCode, but gets hosed after. Shutting down VSCode doesn't fix the problem, but logging out does. |
@BurtHarris this should now be fixed. Please give try to typescript@next to see if it helps |
TypeScript Version: 2.3.4
NPM version: 5.0.4
Repo
app.ts
:tsconfig.json
package.json
:With code open, open the ts file.
In the a terminal for the current workspace, run
npm install
Bug
Here are the file handles:
and the process info for pid
21136
:Seems that the tsserver is holding onto these files, breaking npm install
The text was updated successfully, but these errors were encountered: