Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intellisense not working #88346

Closed
sshanzel opened this issue Jan 9, 2020 · 5 comments
Closed

Intellisense not working #88346

sshanzel opened this issue Jan 9, 2020 · 5 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) javascript JavaScript support issues upstream-issue-linked This is an upstream issue that has been reported upstream

Comments

@sshanzel
Copy link

sshanzel commented Jan 9, 2020

We have written the needed data into you
Issue Type: Bug

I'm working now in a React App which i haven't been doing for quite some time. Now intelli-sense doesn't work for it. The File Association is JavaScript React. I've tried removing all the extensions, then add one by one, es6 snippets, etc. Still nothing happens. I've tried re-installing VS Code but no luck.

This is a fresh project using CRA. I've opened my different projects, it just doesn't work on my React Projects. A simple Vanilla JS Project works perfectly fine.

VS Code version: Code 1.41.1 (26076a4, 2019-12-18T14:58:56.166Z)
OS version: Windows_NT x64 10.0.18362

System Info
Item Value
CPUs Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2208)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 31.74GB (13.49GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (11)
Extension Author (truncated) Version
simple-react-snippets bur 1.2.2
node-snippets chr 1.0.0
npm-intellisense chr 1.3.0
vscode-eslint dba 2.0.13
es7-react-js-snippets dsz 2.5.0
prettier-vscode esb 3.18.0
vscode-azureappservice ms- 0.16.2
azure-account ms- 0.8.8
debugger-for-chrome msj 4.12.4
LiveServer rit 5.6.1
autoimport ste 1.5.3

Reverting back to 1.40.2 has worked for me temporarily. Disabled auto-updates.

@mjbvz
Copy link
Collaborator

mjbvz commented Jan 9, 2020

Where is your code stored? Somewhere besides the c: drive?

@mjbvz mjbvz added javascript JavaScript support issues info-needed Issue requires more information from poster labels Jan 9, 2020
@sshanzel
Copy link
Author

sshanzel commented Jan 9, 2020

It resides in a different drive. Specifically D: while the VS Code is at C: drive.

@mjbvz
Copy link
Collaborator

mjbvz commented Jan 9, 2020

Duplicate of microsoft/TypeScript#35512

To workaround this, upgrade your workspace to use typescript@next by installing this extension

@mjbvz mjbvz closed this as completed Jan 9, 2020
@mjbvz mjbvz added *duplicate Issue identified as a duplicate of another issue(s) upstream-issue-linked This is an upstream issue that has been reported upstream and removed info-needed Issue requires more information from poster labels Jan 9, 2020
@sshanzel
Copy link
Author

sshanzel commented Jan 9, 2020

Yeah based from what i have observed it runs a process endlessly some for initializing and some is updating, both are for ts and js things (probably the problem is up there, as what i can also see from your referenced issue). Thanks a lot for the feedback. Will try the work around later and give some info if something comes up.

@sshanzel
Copy link
Author

It worked! Thanks!

@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) javascript JavaScript support issues upstream-issue-linked This is an upstream issue that has been reported upstream
Projects
None yet
Development

No branches or pull requests

2 participants