TypeScript Version: 3.7.0-dev.20190922
Search Terms:
Repo
npx create-react-app my-app --typescriptmy-app in VS Codeapp.tsxadd.ts with the content:```ts
export function add() {}
```
Run the go to project configuration command in VS Code with add.ts open:
Now go back to App.tsx and try using completions to add an auto import for add
Here are the logs:
log.txt
This repos for me with 3.6.3 and for very simple projects like the following:
tsconfig.js
{
"compilerOptions": {
"module": "commonjs",
"target": "es2016",
"jsx": "react"
}
}
src/main.ts
export function foo() {
add
}
src/add.ts (must be newly created)
export function add() { }
I don't know why we haven't seen this reported on the VS Code side (to my knowledge) but this bug is really annoying. @RyanCavanaugh @sheetalkamat I think this is worth at least investigating for a 3.6.x recovery
@mjbvz in the logs you showed there is only updateOpen but directory watcher for wild card directories is never invoked and that's the reason project doesn't know about app.tsx being part of it..
Info 80 [11:20:43.245] request:
{"seq":14,"type":"request","command":"updateOpen","arguments":{"changedFiles":[],"closedFiles":[],"openFiles":[{"file":"/Users/matb/projects/san/sub/my-app/src/add.ts","fileContent":"","scriptKindName":"TS","projectRootPath":"/Users/matb/projects/san/sub/my-app"}]}}
When I repro your scenario (simple one) I don't see that behavior...

This was with the latest VS Code 1.39 insiders for me with MacOS 10.14.6. I've been able to repo the create-react-app issues it on two macs. Let me give it a quick try on my windows vm too
Seems to work ok on windows using create-react-app
This could be related to our electron update (which goes from node 10.11 to node 12.4). I can't seem to repo with the current stable VS Code builds using typescript@next
It definitely happens pretty consistently on mac VS Code insiders for me though. @RyanCavanaugh We need to investigate this before VS Code 1.39 ships
edit
The bug also repos using TS 3.5.3 so it does look more like an environment issue.
Possibly relevant: https://github.com/nodejs/node/issues/29460 . We should be able to confirm/disprove this theory by running the same version of TS Server on MacOS using node 10.11 and Node 12.4 and seeing if the behavior is different
We have reverted our Electron update for this release as this bug also effects other extensions
Closing this TS side issue in favor of the VS Code issue: https://github.com/microsoft/vscode/issues/81516
This is still an issue for me, running the latest stable VSCode version. @mjbvz was there any regressions since it was fixed in electron 6?
@danilofuchs Please open a new issue
Most helpful comment
This is still an issue for me, running the latest stable VSCode version. @mjbvz was there any regressions since it was fixed in electron 6?