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 is Broken for Packagees #210013

Closed
chamalperera opened this issue Apr 10, 2024 · 16 comments
Closed

Intellisense is Broken for Packagees #210013

chamalperera opened this issue Apr 10, 2024 · 16 comments
Assignees
Labels
info-needed Issue requires more information from poster

Comments

@chamalperera
Copy link

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

  • VS Code Version: 1.88.0
  • OS Version: Windows_NT x64 10.0.22631

Steps to Reproduce:

  1. I have NPM Intellisense installed in my VS Code.
  2. I am developing a ReactJS project.
  3. I have installed Material UI packages through NPM
  4. Use the components available in the Material UI
  5. When I typed a part of the name of a component, the intellisense gave me the suggestions from different packages
  6. I then updated the VS Code to the latest release (v1.88)
  7. And after that when I tried to use the components, the intellisense does not gives me the correct suggestions.

image
image

@gjsjohnmurray
Copy link
Contributor

Probably microsoft/TypeScript#58113 (comment)

@steeljustify
Copy link

I have no intellisense for anything at all. Not tsconfig, not package.json, not even for the console object in a js file. The same project intellisense works fine in visual studio and webstorm.

@mjbvz
Copy link
Contributor

mjbvz commented Apr 10, 2024

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

@mjbvz mjbvz added the info-needed Issue requires more information from poster label Apr 10, 2024
@DysektAI
Copy link

DysektAI commented Apr 10, 2024

@mjbvz & @gjsjohnmurray
We started an issue in MUI about this, because it seems to only affect certain packages.
Not sure if there is already an existing issue for this or if this is where we should tag to but for now the easiest workaround is to downgrade to 1.87.2 we found

I can confirm that the issue still is persistent and not fix currently in the 1.89.0 (Insiders) the MUI imports still have the same issues.

Imports work in ts/tsx but do not resolve properly in js/jsx for MUI Specifically at least
.ts / .tsx works correctly as expected:
image

.js / .jsx does not work correctly:
image

Edit: Add info
Version: 1.89.0-insider (user setup)
Commit: 7eba2d2
Date: 2024-04-10T05:50:02.508Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631

Would love to find a main issue to tag for this to get fixed quickly! Thank you! 😄
mui/material-ui#41802

@mjbvz
Copy link
Contributor

mjbvz commented Apr 10, 2024

@lyricalcasanova microsoft/TypeScript#58113 but this user isn't seeing any intellisense so possible not related

@DysektAI

This comment has been minimized.

@mjbvz

This comment has been minimized.

@DysektAI

This comment has been minimized.

@mjbvz

This comment has been minimized.

@DysektAI

This comment has been minimized.

@mjbvz

This comment has been minimized.

@DysektAI

This comment has been minimized.

@chamalperera
Copy link
Author

Hi @mjbvz & @lyricalcasanova

It seems it is an issue with the latest release of VS Code v1.88.0. I have gone through all the comments @lyricalcasanova provided, and thanks so much for giving many details of the issue.

I have installed the JavaScript and TypeScript Nightly extension into my VSCode and selected the VSCode version. But I am still having the same issue, it does not show me the correct suggestions. Have I done it incorrectly? Or do we have workaround for this issue? Or do we have to wait until the next release?

image

@DysektAI
Copy link

If all else is failing you can also attempt to revert back to 1.87.2 of VS Code which is confirmed to be working without the extension (Don't forget to disable automatic updates)

If the issue still persists, most likely you need to install the packages again in the root of your project where your package.json is located execute the command below and it will install all the packages required for mui if not already install and give an error if there are any:
npm install @mui/material @emotion/react @emotion/styled

(I accidentally did this a few times while pulling my original code and forgetting to reinstall the deps so some of my tests I realized were failing no matter what because the packages didn't exist in my project)

@mjbvz
Copy link
Contributor

mjbvz commented Apr 11, 2024

@chamalperera Does any IntelliSense work? Try opening an empty javascript or typescript file and triggering suggestions

Also did you test in the latest insiders build?

@chamalperera
Copy link
Author

Hi @mjbvz & @lyricalcasanova,

I have updated the VS Code to the lastest release v1.88.1 which resolves the issue. I can confirm the auto imports are now working. I have tested it aftre uninstalling the TypeScript & JavaScript Nightly extension, which @lyricalcasanova suggested earlier as a workaround.

If VS Code is updated to v1.88.1, issue should be gone

@microsoft microsoft locked and limited conversation to collaborators Jun 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

5 participants