Closed
Description
TypeScript Version: 3.7.0-dev.20190922
Search Terms:
- create-react-app
- project configuration
- tsconfig
Repo
-
npx create-react-app my-app --typescript
-
Open
my-app
in VS Code -
Open
app.tsx
-
Now create a new file next to it called
add.ts
with the content:export function add() {}
-
Run the
go to project
configuration command in VS Code withadd.ts
open:- 🐛 Says it's not part of any configured project
-
Now go back to
App.tsx
and try using completions to add an auto import foradd
- 🐛 Auto import never works (unless you add an import manually)
Here are the logs:
log.txt
Metadata
Metadata
Assignees
Labels
Type
Projects
Relationships
Development
No branches or pull requests
Activity
mjbvz commentedon Sep 23, 2019
This repos for me with 3.6.3 and for very simple projects like the following:
tsconfig.js
src/main.ts
src/add.ts
(must be newly created)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
sheetalkamat commentedon Sep 23, 2019
@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 aboutapp.tsx
being part of it..When I repro your scenario (simple one) I don't see that behavior...
mjbvz commentedon Sep 23, 2019
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
mjbvz commentedon Sep 23, 2019
Seems to work ok on windows using create-react-app
mjbvz commentedon Sep 26, 2019
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: nodejs/node#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
[-]create-react-app --typescript project not picking up new ts files in vscode [/-][+]TS Server not picking up new TS files in vscode on MacOS[/+]mjbvz commentedon Sep 30, 2019
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: microsoft/vscode#81516
danilofuchs commentedon Mar 28, 2020
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?
mjbvz commentedon Mar 31, 2020
@danilofuchs Please open a new issue