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

Abierto
#43,375 9 comentarios 0 reacciones 1 asignado Ver en GitHub

@rakatyal ya está trabajando en esto.

Desde el 10/8/2021.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

Lenguaje dominante
Go
Estrellas
111k
Forks
14.4k
Merge medio
1 d 19 h
PR fusionados (30 d)
117

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de microsoft/TypeScript

Todos los issues de microsoft/TypeScript

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.