Intellisense does not pickup Typescript 3 references

[mjbvz]

From @tommedema on August 27, 2018 3:12

• VSCode Version: 1.26.1
• OS Version: OSX High Sierra

Steps to Reproduce:

1. git clone git@github.com:tommedema/serverless-mono-example.git
2. cd serverless-mono-example && yarn install && code .
3. if you change a typing in package random, it is not picked up by intellisense in typescript packages that reference to it in the same workspace (e.g. sls-random); you'd have to compile first

for example, change fetchRandomNumber in random to return a Promise<string>, and sls-random still expects a Promise<number>

Note that sls-random is connected with random through Typescript 3 references:

{
  "extends": "../../tsconfig.settings.json",
  "compilerOptions": {
    "outDir": "dist",
    "rootDir": "src"
  },
  "references": [
    { "path": "../random" }
  ]
}

And therefore intellisense should pickup the referenced typings dynamically.

Does this issue occur when all extensions are disabled?: Yes

Copied from original issue: microsoft/vscode#57242

[ajafff]

From the TypeScript Handbook: https://www.typescriptlang.org/docs/handbook/project-references.html

Because dependent projects make use of .d.ts files that are built from their dependencies, you’ll either have to check in certain build outputs or build a project after cloning it before you can navigate the project in an editor without seeing spurious errors. We’re working on a behind-the-scenes .d.ts generation process that should be able to mitigate this, but for now we recommend informing developers that they should build after cloning.

[donaldpipowitch]

I have a similar problem. Is this a duplicate or is my example different? https://github.com/donaldpipowitch/typescript-refactoring-references

[chriswoodle]

Getting the same issue, have to compile a project for its type intellisense in other projects to update when changes are made.

It's a big problem for a repo I'm working on that has 19 different package references. When running the tsc watch, it can take over 15 sec for a typing to update.

[MLoughry]

Running into the same issue in our mono-repo.

This is labeled as VS Code Tracked, but the linked bug in their repo is closed. @mjbvz, is this something that needs to be fixed in Typescript or VS Code?

[chriswoodle]

Correct me if I’m wrong, but since vscode relys on TSServer for providing information for intellesence, and the new References feature uses the output .d.ts for each project for typing; the TSServer would have to have a way to bypass the .d.ts files and directly go to the source to determine typings. I would think that this is a TS issue and not only VSCode.

[tommedema]

Anything I can do to help this get fixed?

[chriswoodle]

@mjbvz Any updates? Or a pointer to progress on the behind-the-scenes .d.ts generation process @ajafff? Thanks.