-
Notifications
You must be signed in to change notification settings - Fork 28.1k
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
Snap: Failed to read user shell environment #72042
Comments
@dbaeumer What can the user do to figure out what's wrong? |
@RMacfarlane took that over. We might want to consider changing the publisher |
If there anything in the JSHint output panel? |
@NatoBoram do you have jshint itself installed? Your workspace doesn't have a node_modules folder. |
Also, can you reproduce with VS Code without Snap? https://update.code.visualstudio.com/latest/linux-x64/insider |
@dbaeumer JSHint was installed globally. The workspace isn't a NodeJS project. jshint --version
jshint v2.10.2 @joaomoreno |
@NatoBoram does it work if you install jshint locally? |
Yes, it works when installed locally. |
@NatoBoram Do you use NVM? If you open the Developer Tools and run |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Reopening. @joaomoreno and I looked into this and the problem seems to be that the environment is not correctly sourced when running out of a snap which makes the server fail looking up global node moddules. |
Also faced this issue. the problem is with gnome launcher |
I have a similar issue but the above does not fix it. |
I should have said "none of my npm scripts work |
Root cause: https://forum.snapcraft.io/t/new-store-automated-review-rule-is-incorrect/12963/27?u=joaomoreno Fix should come soon from the snapcraft team! |
1.34.0-insider
56f1b47 x64Ubuntu 18.04.2 LTS x86_64
Steps to Reproduce:
dbaeumer.jshint
Does this issue occur when all extensions are disabled?: N/A
I also reported it in microsoft/vscode-jshint#71, but it's probably unrelated to the extension itself.
The text was updated successfully, but these errors were encountered: