You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a documentation issue linked from an error thrown within js-debug
You've landed on this issue because we weren't able to enable auto attach on your machine.
This is because auto attach now works by adding a "bootloader" file that's required in your Node.js scripts. Prior to Node 12, this path did not support spaces (nodejs/node#12971) and would cause any node program to fail if we tried to use them.
Because of the risk of 'breaking' the integrated terminal in this way, js-debug will not enable auto attach if both:
there is a space in the extension storage path (i.e. the location where VS Code is installed);
and we see that the version of node on your path is less than version 12, or we don't find node on your path at all.
There are two things you can do to get around this issue:
Update to a Node version >12
If the error is not correct (which may happen when using .rc-file based version managers like nvm or nvs), you can still enable auto attach by running the command Debug: Force Enable Auto-Attach from the command palette. If this breaks your setup, you can restore your state by setting auto attach to disabled and then reloading the VS Code window.
The text was updated successfully, but these errors were encountered:
You've landed on this issue because we weren't able to enable auto attach on your machine.
This is because auto attach now works by adding a "bootloader" file that's required in your Node.js scripts. Prior to Node 12, this path did not support spaces (nodejs/node#12971) and would cause any
node
program to fail if we tried to use them.Because of the risk of 'breaking' the integrated terminal in this way, js-debug will not enable auto attach if both:
node
on your path is less than version 12, or we don't findnode
on your path at all.There are two things you can do to get around this issue:
disabled
and then reloading the VS Code window.The text was updated successfully, but these errors were encountered: