-
Notifications
You must be signed in to change notification settings - Fork 12.8k
3.7.2 — Cannot read property 'path' of undefined #35091
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
@David-Else Thank you for testing this and collecting the logs. That error definitely would explain the errors you are seeing in VS Code. I've moved the issue over the to TypeScript repo for further follow up |
Some users are setting weird errors related to untitled TS files. In some of these cases (such as microsoft/TypeScript#35091) we see a untitled file being sent to the tsserver without the `inMemoryResourcePrefix`. I can't figure out how to get into this state but am removing the gating that *could* perhaps cause use not to set `inMemoryResourcePrefix`. This gating targets TS 2.7 or older, which telemetry shows very, very few users are still enabling in their workspaces
@mjbvz The main issue here is that there is no |
Thanks. The missing |
I still got the error in the insiders build, version 1.41.0-insiders |
same here |
In 1.40.2 I still have the same error, TS language can't start. Later edit: So I went over and disabled all extensions and then re-enabled one by one. GitLens extension was causing the TS language server to crash for some reason. Later later edit: Line and file annonations from GitLens seem to be the problem. I've disabled them from extension's settings and now the language server starts correctly. This annotation seem to be a performance hit as well for the quick suggetions. |
Just to add to this, I see similar symptoms and a resolution after disabling GitLens when using TS 3.7.2. |
@sheetalkamat Please re-open this. This error is NOT fixed using |
From microsoft/vscode#84171
TypeScript Version: 3.7.2
Search Terms:
Bug
When working with an untitled file in VS Code, a user reports seeing this error:
Since VS code 1.40, we treat all errors in
updateOpen
as fatal so we restart the server at this point (and promptly crash again)This is a very similar error to #35001 but the user does not appear to have tslint installed (TSLint logs quite a bit and we also don't see any plugin load requests)
/cc @sheetalkamat
The text was updated successfully, but these errors were encountered: