"Project does not contain document" Error Causes Types to Stop Resolving in VS Code #38366
Labels
Bug
A bug in TypeScript
Crash
For flagging bugs which are compiler or service crashes or unclean exits, rather than bad output
Fix Available
A PR has been opened for this issue
Milestone
TypeScript Version: 3.9.1-rc
Search Terms:
VS Code, Go to Definition, Go to Type Definition
Code
I'm not sure how to self-contain this, but within a given package I am:
CustomDialog
CustomDialogProps
(this navigation fails soon after TS Server restart)Expected behavior:
Types defined within a given package are always navigable via VS Code.
Actual behavior:
I have an instance of navigating to type that works for a while after restarting TS server but then soon fails consistently. At some point navigation to a given type fails with the following error in the TS Server log. I am not sure why this error would occur given that the interface is defined and captured by the
tsconfig.json
and output intolib
.Playground Link:
I'm not sure how to replicate this kind of issue in Playground, but I do have a local repro that I can get to trigger consistently. I also have TS Server logs I can provide privately.
Related Issues:
I tried searching issues for "Go to definition" and didn't see anything applicable. @DanielRosenwasser if there are any further steps I can take to help, please let me know!
The text was updated successfully, but these errors were encountered: