microsoft / microsoft/TypeScript

Intellisense cannot find referenced projects in VS, even after successful build

Aperta
#43,375 9 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@rakatyal ci sta già lavorando.

Dal 10/8/2021.

Needs Investigation
Lingua principale
Go
Stelle
111k
Fork
14.3k
Merge medio
2g 4h
PR unite (30g)
132

Descrizione

🔎 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.

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.