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 #87680

Closed
MyronLi opened this issue Dec 25, 2019 · 16 comments
Closed

Intellisense not working #87680

MyronLi opened this issue Dec 25, 2019 · 16 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster javascript JavaScript support issues upstream-issue-linked This is an upstream issue that has been reported upstream

Comments

@MyronLi
Copy link

MyronLi commented Dec 25, 2019

Issue Type: Bug

If the workspace contains a project creating with create-react-app, intellisense is not working(always "loading....").

VS Code version: Code 1.41.0 (9579eda, 2019-12-11T18:37:42.077Z)
OS version: Windows_NT x64 6.1.7601

System Info
Item Value
CPUs Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz (4 x 2494)
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: unavailable_off
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: unavailable_off
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: unavailable_off
Load (avg) undefined
Memory (System) 7.94GB (1.98GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (7)
Extension Author (truncated) Version
npm-intellisense chr 1.3.0
vscode-eslint dba 2.0.11
vscode-html-css ecm 0.2.3
vscode-npm-script eg2 0.3.10
prettier-vscode esb 3.18.0
vscode-typescript-tslint-plugin ms- 1.2.3
debugger-for-chrome msj 4.12.3
@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Dec 25, 2019
@inifawaz
Copy link

I also experienced the same thing

@VipulSoni-Dev
Copy link

same thing here

@fushihara
Copy link

I am in a similar state.
Even if you press ctrl + space, only loading is displayed, and it takes about 10 seconds until intellisence is displayed.
Also, the update of the underline meaning of the error warning in the source code is very painful, about 10 seconds later.
I've never had to wait on the same machine, on the same project.
typescript 3.7.3

@kieferrm kieferrm removed the terminal General terminal issues that don't fall under another label label Dec 26, 2019
@VitaminCtea
Copy link

There is no intellisense in the React file, other files are normal. The vue or angular files have not been tried!

@VipulSoni-Dev
Copy link

VipulSoni-Dev commented Dec 29, 2019

for me it works after installing npm and npm intellisense extensions in my new VSCode..
try this if you are working on react-native ,react , or node.js

@MyronLi
Copy link
Author

MyronLi commented Dec 29, 2019

for me it works after installing npm and npm intellisense extensions in my new VSCode..
try this if you are working on react-native ,react , or node.js

try react that creating by create-react-app.

@VitaminCtea
Copy link

@sonivipul89 Back to version 1.40 intellisense is work. This did not take effect in the latest version 1.41.
I had to disable automatic updates and keep them at version 1.40. Wait until officials fix the problem and then update to the latest version.

@VitaminCtea
Copy link

@MyronLi It's a project that's been generated with React scaffolding, But it doesn't have much to do with how the project is generated.
There should be a problem with the internal build of vscode, Look forward to the official restoration of it.

Note: In version 1.40, this problem did not occur

@mjbvz
Copy link
Collaborator

mjbvz commented Dec 30, 2019

@MyronLi Is your core stored on something other than the c: drive?

@mjbvz mjbvz added javascript JavaScript support issues info-needed Issue requires more information from poster labels Dec 30, 2019
@MyronLi
Copy link
Author

MyronLi commented Dec 30, 2019

Everything for vscode store on c: drive. @mjbvz
Installation dir: installation "C:\Program Files\Microsoft VS Code\Code.exe"
Config dir: C:\Users\%USERNAME%\.vscode
Data dir: C:\Users\%USERNAME%\AppData\Roaming\Code
But npm install on d: drive
package.json
{
"name": "react-app-demo",
"version": "0.1.0",
"private": true,
"dependencies": {
"@testing-library/jest-dom": "^4.2.4",
"@testing-library/react": "^9.4.0",
"@testing-library/user-event": "^7.2.0",
"classnames": "^2.2.6",
"react": "^16.12.0",
"react-dom": "^16.12.0",
"react-scripts": "3.3.0"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": "react-app"
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}

@MyronLi
Copy link
Author

MyronLi commented Dec 30, 2019

node version: v10.17.0 manged by nvm-windows. @mjbvz

@VitaminCtea
Copy link

There are two solutions to the problem of intellisense not working:

  1. Back to version 1.40, and then disable automatic updates in the settings.json file.
  2. If you're friends with version 1.41, you can fix the problem by installing the JavaScript and TypeScript Nightly plugin

Self test, both are effective. I hope I can help others who have the same problem as me

@MyronLi
Copy link
Author

MyronLi commented Dec 31, 2019

Thank you for feedback. @VitaminCtea
I had backed to version 1.40.

@zhanyuzhang
Copy link

zhanyuzhang commented Dec 31, 2019

@VitaminCtea It's now normal after installing JavaScript and TypeScript Nightly .Thx

@VitaminCtea
Copy link

@MyronLi @zhanyuzhang Well done!

@mjbvz
Copy link
Collaborator

mjbvz commented Jan 23, 2020

Duplicate of microsoft/TypeScript#35512

Should be fixed in VS Code insiders

@mjbvz mjbvz closed this as completed Jan 23, 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 labels Jan 23, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 8, 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) info-needed Issue requires more information from poster 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

8 participants