microsoft / microsoft/TypeScript
Intellisense cannot find referenced projects in VS, even after successful build
@rakatyal is already working on this.
Since Aug 10, 2021.
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
🔎 Search Terms
intellisense references
🕗 Version & Regression Information
Typescript Version: 3.9.2 and 4.2.3 with Visual Studio 16.5.4 and 16.9.2
These are the VS/Typescript versions we have access to; our codebase would not build on an older version of TS.
⏯ Playground Link
As an intellisense issue in VS, the Playground is not really relevant here.
💻 Code
See https://github.com/markboyall/typescript-intellisense-break-repro
🙁 Actual behavior
In this minimal sample, see PageClass.ts. The Class import has no Intellisense support.
Intellisense cannot locate any modules in the referenced projects. Even after running the build and restarting VS, Intellisense is not supplied for the projects. Note that in the actual build this succeeds without error which I feel eliminates any potential of the tsconfig being incorrect.
🙂 Expected behavior
As https://github.com/microsoft/TypeScript/pull/32028 is resolved, expect that when opening VS, intellisense is supplied for all modules. Or at the very least, this should begin working when the build is run (not unreasonable as some of our code is generated in MSBuild so Intellisense can't be expected to supply it before that; however this does not apply to the minimal sample).
I've manually verified a few things like that the .d.ts files are in the right place with the right name, and contain the right modules (would have expected the build to fail if these do not work anyway).
Not sure what extra information can be supplied here.
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.
Assessment
This issue has not been assessed yet.