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

Node not found after upgrading the IDE #105128

Closed
frnmjn opened this issue Aug 21, 2020 · 6 comments
Closed

Node not found after upgrading the IDE #105128

frnmjn opened this issue Aug 21, 2020 · 6 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Milestone

Comments

@frnmjn
Copy link

frnmjn commented Aug 21, 2020

  • VSCode Version: 1.48.0
  • OS Version: elementary OS 5.1 Hera

Steps to Reproduce:
I use asdf to have a specific node version for each workspace. When i run the mocha test laucher i receive this error.
image
If I downgrade the version to 1.46.1 it restart to work

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

@weinand weinand assigned connor4312 and unassigned weinand Aug 21, 2020
@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Aug 21, 2020
@connor4312
Copy link
Member

Does /home/ejf/.asdf/shims/node exist? Or is it a symlink or something?

@connor4312 connor4312 added the info-needed Issue requires more information from poster label Aug 21, 2020
@frnmjn
Copy link
Author

frnmjn commented Aug 24, 2020

yes it exists and is not a simbolic link
image

@connor4312 connor4312 removed the info-needed Issue requires more information from poster label Aug 24, 2020
@connor4312 connor4312 added this to the August 2020 milestone Aug 24, 2020
@connor4312
Copy link
Member

Thanks @ejf-coders51. Unfortunately trying asdf in a container locally, I didn't hit this. I made a build of the extension that adds additional information to the error message, can you give it a shot? https://memes.peet.io/img/105128-js-debug.vsix You can install it by hitting F1 and then Install from VSIX.

Also, as a workaround, you can set debug.javascript.usePreview: false in your user settings to use the old debugger until we get this fixed.

@connor4312 connor4312 added the info-needed Issue requires more information from poster label Aug 24, 2020
@frnmjn
Copy link
Author

frnmjn commented Aug 25, 2020

image

i've installed the vsix. In the terminal npm is working. it seams that the debugger is not runned in the project folder

@connor4312 connor4312 removed the info-needed Issue requires more information from poster label Aug 25, 2020
@connor4312
Copy link
Member

Ah, I see, thanks. Two things, in addition to usePreview: false, you can use to get around it:

  1. Set nodeVersionHint: 12 in your package.json
  2. Start code from a terminal so that in inherits its environment, rather than from the UI

I will close this as a dupe of microsoft/vscode-js-debug#717, which should fix this.

/duplicate

@github-actions github-actions bot locked and limited conversation to collaborators Oct 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants
@weinand @connor4312 @frnmjn and others