Cannot find module bootloader.js #374

jasonwilliams · 2020-03-03T16:29:14Z

Lately I've been getting this when trying to use the debugger (which now also doesn't work)

Error: Cannot find module '/Users/[User]/.vscode/extensions/ms-vscode.js-debug-nightly-2020.3.217/src/bootloader.js'
Require stack:
- internal/preload
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:954:17)
    at Function.Module._load (internal/modules/cjs/loader.js:847:27)
    at Module.require (internal/modules/cjs/loader.js:1016:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:1285:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:439:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:66:3)
    at internal/main/run_main_module.js:7:1 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 'internal/preload' ]
}

pwa-node doesn't work at all now :(
But i can't reproduce it on a public repo (it may not be related to the above)

The text was updated successfully, but these errors were encountered:

connor4312 · 2020-03-03T16:40:37Z

What does ls ~/.vscode/extensions/ms-vscode.js-debug-nightly-2020.3.217/src say? The bootloader file is present for me there, wonder if you got a corrupted install somehow.

jasonwilliams · 2020-03-03T19:45:38Z

It does show when I do that (which makes it more odd), so I’m not sure. I’ll see if it keeps happening, it can be inconsistent

connor4312 · 2020-03-05T18:50:04Z

What might have happened is that the extension activated and was then updated without reloading / in another vscode window. Then the old extension folder was deleted, which caused the bootloader script disappeared. I can't seem to get into that state playing around locally, but that's one idea...

jasonwilliams · 2020-03-05T20:13:31Z

Yeah there’s a chance of that, is there a way for me to debug if that’s the case? I’ll look out for it again

connor4312 · 2020-03-05T22:22:51Z

If you see it happen again, take note of the version in the path it's looking for, then open the extension panel in vscode and see what version of the extension it says is installed.

phyllisstein · 2020-05-01T03:28:13Z

I’m seeing something quite similar in my project. I’ve got a tasks.json file with the following configuration:

{
  "version": "2.0.0",
  "tasks": [
    {
      "type": "npm",
      "script": "start:dev",
      "problemMatcher": {
        "owner": "node",
        "fileLocation": "absolute",
        "pattern": {
          "regexp": "^🚨  (.*?):((\\d):(\\d):)? (.*)$",
          "line": 3,
          "column": 4,
          "file": 1,
          "message": 5
        },
        "background": {
          "activeOnStart": true,
          "beginsPattern": "^Server running at",
          "endsPattern": "^✨  Built in"
        }
      },
      "presentation": {
        "echo": true,
        "reveal": "always",
        "focus": false,
        "panel": "shared",
        "showReuseMessage": true,
        "clear": false
      },
      "label": "npm: start:dev",
      "detail": "Start the Parcel development server",
      "isBackground": true
    },
  ]
}

When I run the task, I see the following messages in VSCode’s terminal pane:

> Executing task: npm run start:dev <

internal/modules/cjs/loader.js:979
  throw err;
  ^

Error: Cannot find module '/var/folders/82/x75jd1fx0jj40t9s7tnghvxc0000gp/T/vscode-js-debug-bootloader.js'
Require stack:
- internal/preload
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:976:15)
    at Function.Module._load (internal/modules/cjs/loader.js:859:27)
    at Module.require (internal/modules/cjs/loader.js:1036:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:1292:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:439:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:71:3)
    at internal/main/run_main_module.js:7:1 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 'internal/preload' ]
}
The terminal process terminated with exit code: 1

Terminal will be reused by tasks, press any key to close it.

The same thing happens when I run an automatically detected and configured task:

> Executing task: npm run build <

internal/modules/cjs/loader.js:979
  throw err;
  ^

Error: Cannot find module '/var/folders/82/x75jd1fx0jj40t9s7tnghvxc0000gp/T/vscode-js-debug-bootloader.js'
Require stack:
- internal/preload
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:976:15)
    at Function.Module._load (internal/modules/cjs/loader.js:859:27)
    at Module.require (internal/modules/cjs/loader.js:1036:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:1292:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:439:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:71:3)
    at internal/main/run_main_module.js:7:1 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 'internal/preload' ]
}
The terminal process terminated with exit code: 1

Terminal will be reused by tasks, press any key to close it.

When I run the task with the Developer Tools open, I see the following logged to the browser console:

log.ts:197   ERR ioctl(2) failed, EBADF: Error: ioctl(2) failed, EBADF
    at UnixTerminal.resize (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/node_modules.asar/node-pty/lib/unixTerminal.js:238:13)
    at e.resize (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:3342:64)
    at e.setDimensions (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4344:261)
    at e._resize (file:///Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:4442:108)

I don’t really have a great sense of what all that could mean, I’m afraid. I can confirm that there is no vscode-js-debug-bootloader.js file in that temporary folder, but I’m not sure how to troubleshoot beyond that.

My VSCode version info is:

Version: 1.45.0-insider
Commit: 2a36b7d0d527bf408bae4f96b8386db9d9455113
Date: 2020-05-01T01:50:35.321Z (1 hr ago)
Electron: 7.2.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.4.0

I currently have v2020.4.3017 of this package installed.

connor4312 · 2020-05-01T04:17:16Z

Because this is happening in tasks, I think you're running into microsoft/vscode#96375. You should be able to fix this by:

Setting debug.node.autoAttach to "disabled" (to clear previous bad state)
Setting it back to on or off, as you prefer
Using the⚠️ icon on the top right to relaunch terminals as desired (or just reopen/reload VS Code)

phyllisstein · 2020-05-01T04:47:05Z

That did it! Thank you so much. I guess the two issues weren’t as similar as they looked. 🙊

connor4312 · 2020-05-01T04:53:39Z

No worries, thanks for the detailed information 🙂

jasonwilliams · 2020-05-01T07:56:54Z

Because this is happening in tasks, I think you're running into microsoft/vscode#96375. You should be able to fix this by:

Setting debug.node.autoAttach to "disabled" (to clear previous bad state)

Setting it back to on or off, as you prefer

Using the⚠️ icon on the top right to relaunch terminals as desired (or just reopen/reload VS Code)

This would make a great FAQs answer

connor4312 · 2020-05-01T14:38:10Z

The root cause got fixed in the commit that closed that bug, so it should not be an ongoing issue--this is the first report community report I've received of it so far 🙂

connor4312 · 2020-05-05T18:41:18Z

I discovered another case where this can happen with auto attach on extension version upgrade (microsoft/vscode#96929). I applied a fix for it in the linked commit; you may see this one more time on the next version update, but after today's nightly (which will be version 2020.5.517) it should no longer be an issue.

Verification steps:

Install any older version of js-debug
Turn on auto attach. Run node and make sure it can attach.
Update to a newer js-debug version, and reload the window
Run node again. It should attach without errors.

paulsimongb · 2020-07-09T15:36:59Z

Tried that and I am still getting this error. I have checked the file system and the file exists, so can't it find it?

connor4312 · 2020-07-09T16:14:55Z

See your issue here: microsoft/vscode#101996

rossmc · 2020-07-13T08:41:01Z

Issue still occurs for me with latest stable version of node and vscode...

$ yarn
internal/modules/cjs/loader.js:969
  throw err;
  ^

Error: Cannot find module '/var/folders/lp/_d8xd7zs60g73wlpxk2dwh_h0000gn/T/vscode-js-debug-bootloader.js'
Require stack:
- internal/preload
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:966:15)
    at Function.Module._load (internal/modules/cjs/loader.js:842:27)
    at Module.require (internal/modules/cjs/loader.js:1026:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:1278:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:439:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:71:3)
    at internal/main/run_main_module.js:7:1 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 'internal/preload' ]
}
$ node -v
v12.18.2

sudo yarn works for some reason though ??

ochicf · 2020-07-13T11:21:20Z

I have a similar issue that started after updating VSCode to the latest version. I did not change the launch.json and it was working before (hence, it is correct).

The issue happens when opening a terminal in VSCode. The following error is thrown:

internal/modules/cjs/loader.js:670
    throw err;
    ^

Error: Cannot find module '/var/folders/4g/885bdns57cqf1cqzx8dw0vch0000gn/T/vscode-js-debug-bootloader.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:668:15)
    at Function.Module._load (internal/modules/cjs/loader.js:591:27)
    at Module.require (internal/modules/cjs/loader.js:723:19)
    at Module._preloadModules (internal/modules/cjs/loader.js:945:12)
    at loadPreloadModules (internal/bootstrap/pre_execution.js:363:5)
    at prepareMainThreadExecution (internal/bootstrap/pre_execution.js:61:3)
    at internal/main/run_main_module.js:11:1

And I cannot use the terminal anymore as I guess the configuration is broken:

➜ node -v                           
zsh: command not found: node
➜ nvm current   
none

Information about my setup (from About VSCode):

Version: 1.47.0
Commit: d5e9aa0227e057a60c82568bf31c04730dc15dcd
Date: 2020-07-09T08:01:54.115Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.5.0

Some more info:

I can run everything as normal from the non VSCode terminal (ex: from iTerm2)
I can start a debug session from VSCode as usual and everything seems to be working great (breakpoints, variables, etc.)

connor4312 · 2020-07-13T13:24:52Z

Please set debug.node.autoAttach to disabled for the moment. This will be fixed in the upcoming recovery release.

mikeshot · 2020-07-13T14:16:14Z

Please set debug.node.autoAttach to disabled for the moment. This will be fixed in the upcoming recovery release.

Thank you! Having the same issue & this fixes it (at least for now).

amlcodes · 2020-07-13T15:20:41Z

No luck at all, when launching debugger.

internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module '"/home/node/.vscode-server-insiders/bin/e7920dce7bfd0b707ebfc0a5379c6edd2233e475/extensions/ms-vscode.js-debug/src/bootloader.bundle.js"

launch.json - seems like "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/babel-node" is doing it

{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Launch",
      "type": "node",
      "request": "launch",
      "protocol": "inspector",
      "program": "${workspaceRoot}/src/index.js",
      "stopOnEntry": false,
      "args": [],
      "cwd": "${workspaceRoot}",
      "preLaunchTask": null,
      "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/babel-node",
      "runtimeArgs": [
        "--nolazy"
      ],
      "env": {
        "NODE_ENV": "development"
      },
      "console": "internalConsole",
      "sourceMaps": false,
      "outFiles": []
    }
  ]
}

connor4312 · 2020-07-13T15:37:30Z

@amlcodes you're hitting a version of microsoft/vscode#102035 (comment). The resolution steps in the comment will work for you (just ignore the electron part of it)

aventurella-honey · 2020-07-14T19:20:24Z

I'm seeing the same issue in 1.47.1.

Version: 1.47.1
Commit: 485c41f9460bdb830c4da12c102daff275415b53
Date: 2020-07-13T22:43:02.577Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.5.0

When I launch the debugger in the integrated terminal I get the following error:

env 'NODE_OPTIONS=--require "/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/bootloader.bundle.js"

^ this file exists

cat "/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/bootloader.bundle.js"

But running my action yields this error, it's like the path isn't escaped?

internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module '"/Applications/Visual'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at Module._preloadModules (internal/modules/cjs/loader.js:901:12)
    at preloadModules (internal/bootstrap/node.js:601:7)
    at startup (internal/bootstrap/node.js:273:9)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:622:3)

Setting Debug > JavaScript: Use Preview to false doesn't seem to fix it additionally setting Debug: Node: Auto Attach to disabled or toggling it from on/off -> disabled seems to have no affect. Restarting VS Code additionally doesn't seem to have any affect.

Its' attempting to run under nvm with node version 10.16.3. It was all working prior to VS Code 1.47

When I upgrade to node 12.16.3 it works

connor4312 · 2020-07-14T20:02:34Z

@aventurella-honey your issue is also microsoft/vscode#102035 (comment) (just ignore the electron part)

tehpsalmist · 2020-08-17T18:04:37Z

Sure, I can spare like 5 minutes

connor4312 · 2020-08-17T18:36:11Z

Awesome, thanks, sent a Teams invite to the email on your GH profile

tehpsalmist · 2020-08-29T06:52:02Z

Unfortunately, I'm still having trouble with this. For some reason, most of my workspaces have a non-working terminal and a handful of them work. I've tried the workarounds, and I've tried to replicate that process we (@connor4312 ) did over the screenshare where we installed a later version of the debugger and then turned the autoattach on/off. Either I just can't remember the correct debug package to do that with or the problem is not that uniformly distributed across my machine. Either way, I would really love to get this working again. Any advice is welcome, but ideally a future version of vs code will just have the proper migrations or fixes to make this a non-issue.

connor4312 · 2020-08-29T23:21:39Z

The next version should have the fixes, to be released in about 1.5 weeks. We reintroduce this general strategy, but with many more safeguards and fixes -- tracked in #703

You can probably--I've not tested this--fix it globally by deleting (or renaming first, to be safe) your workspace storage folders to clear temp data. I believe by default on OSX this is ~/Library/Application Support/Code/User/workspaceStorage

tehpsalmist · 2020-08-30T03:22:15Z

Ah, thank you, deleting that directory does seem to have brought a few workspaces back to working condition. If I find more that can't be fixed by the strategies listed above I'll report on it, but for now this seems to have straightened things out for me.

jeffbski-rga · 2020-09-21T20:18:52Z

I am having this error too with the August 2020 release.

LSTL67fchtdd:~/projects/cloud-loadresults [sonar-2020-09-21]$ npm run test:unit
internal/modules/cjs/loader.js:638
    throw err;
    ^

Error: Cannot find module '/var/folders/m3/y7pcwbqj6nq9lrhmff598j74hgrysl/T/vscode-js-debug-bootloader.js'

If I run this in a iterm terminal outside of vscode then everything is fine, so this is something related to vscode.

I do not have the ~/Library/Application Support/Code/User/workspaceStorage folder

connor4312 · 2020-09-21T20:24:26Z

Any chance you have that left over from the June 2020 release? That problem was prevalent before the recovery release there, and since then we'll no longer put the bootloader in a tmpdir.

Do these steps fix the issue? #374 (comment)

jeffbski-rga · 2020-09-21T20:27:52Z

Yes, thanks @connor4312 that fixes it.

rayhatfield · 2021-10-19T21:15:49Z

I'm encountering a variation of this issue with a project that uses Node 10. I think what's happening is the plugin initializes against my default Node version (17.x or whatever) and decides spaces in paths are fine. Then I switch to 10.15 (via nvm) and it chokes on "Application Support":

⟩nvm use
Found '/path/to/project/.nvmrc' with version <10.15.1>
Now using node v10.15.1 (npm v)
internal/modules/cjs/loader.js:583                                                                                       
    throw err;
    ^

Error: Cannot find module '"/Users/ray/Library/Application'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at Module._preloadModules (internal/modules/cjs/loader.js:812:12)
    at preloadModules (internal/bootstrap/node.js:599:7)
    at startup (internal/bootstrap/node.js:273:9)
    at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)

If I remove the NODE_OPTIONS environment variable the error goes away.

⟩echo $NODE_OPTIONS
--require "/Users/ray/Library/Application Support/Code/User/workspaceStorage/746f163c1fc90a7d6784a0a087d9f560/ms-vscode.js-debug/bootloader.js"

If I disable auto-attach it goes away and I can live with that for now, but if someone has a better idea I'm open to suggestions.

connor4312 · 2021-10-19T21:34:17Z

Yea, we don't have any way to detect nvm version changes. All Node version that don't support quotes (<12) are in end of life so I do not plan to go through great lengths to discover a workaround for this.

rayhatfield · 2021-10-19T21:39:40Z

Understood. Posted mostly just to get confirmation that that is what's happening and I'm not missing some obvious fix, and to provide info for future VS Code archaeologists. Thanks.

Porges · 2022-06-08T23:13:39Z

I am getting this constantly, on multiple different codespaces/repos. Is there any current known issue?

Porges · 2022-06-08T23:31:17Z

If anyone else finds this, this comment has the solution: microsoft/vscode#137794 (comment)

JustinGrote · 2022-10-25T20:12:27Z

@Porges this fixes it temporarily but it happens on every codespaces rebuild. Is there a more permanent fix? I tried putting various autoattach settings into my devcontainer file with no luck.

RaviPabari · 2023-01-19T08:37:05Z

Faced same issue with

❯ code --version
1.74.3
97dec172d3256f8ca4bfb2143f3f76b503ca0534
x64

OS: Linux Mint 20.3 x86_64 
Kernel: 5.4.0-124-generic

Unistalling and reinstalling fixed the problem for me.

louwers · 2023-08-05T23:22:21Z

Still running into this and none of the posted solutions seem to work.

I am not even trying to use the debugger, just using npm in the terminal.

Edit: reinstalling the plugin worked.

…Processes) Auto attach would cause things such as Mapshaper's runCommandsXL() to fail, when running in OCI containers, as VSCode would try to attach to exec'ed child processes. See: microsoft/vscode-js-debug#374

shemy-gan · 2024-05-29T13:31:04Z

Linux: Ubuntu 20.04
Node 18.13
Vscode: 1.89.1

do a npm --version, getting below
Error: Cannot find module '/snap/code/155/usr/share/code/resources/app/extensions/ms-vscode.js-debug/src/bootloader.js'
Require stack:

internal/preload
double checked /snap/code/155, does not exist, I think it was removed by auto VSCode update at some point

Austint30 · 2024-07-01T23:13:00Z

Hello,

Seems like this is still an issue in 2024. Getting this output after running npm install <name>:

node:internal/modules/cjs/loader:1189
  throw err;
  ^

Error: Cannot find module '/home/node/.vscode-server/data/User/workspaceStorage/9271fbbe3b75a285e8c4679515f8dd2a/ms-vscode.js-debug/bootloader.js'
Require stack:
- internal/preload
    at Module._resolveFilename (node:internal/modules/cjs/loader:1186:15)
    at Module._load (node:internal/modules/cjs/loader:1012:27)
    at Module.require (node:internal/modules/cjs/loader:1271:19)
    at Module._preloadModules (node:internal/modules/cjs/loader:1653:12)
    at loadPreloadModules (node:internal/process/pre_execution:687:5)
    at setupUserModules (node:internal/process/pre_execution:200:5)
    at prepareExecution (node:internal/process/pre_execution:153:5)
    at prepareMainThreadExecution (node:internal/process/pre_execution:52:10)
    at node:internal/main/run_main_module:13:19 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 'internal/preload' ]
}

Node.js v22.2.0

Disabling and re-enabling auto attach fixes the issue temporarily, but I have to do this every time I start up the dev container.

lamuertepeluda · 2024-07-19T07:26:20Z

I am still having this issue for VSCode 1.91.1 on macOS Sonoma (Apple Silicon).

Trying to debug some (rather complex) jest tests

Error: Jest: Got error running globalSetup - /usr/src/app/test/setup.ts, reason: Command failed: node -r ts-node/register ./src/cli.ts merge-openapi
node:internal/modules/cjs/loader:1148
  throw err;
  ^

Error: Cannot find module '/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/ms-vscode.js-debug/src/bootloader.js'
Require stack:
- internal/preload
    at Module._resolveFilename (node:internal/modules/cjs/loader:1145:15)
    at Module._load (node:internal/modules/cjs/loader:986:27)
    at internalRequire (node:internal/modules/cjs/loader:176:19)
    at Module._preloadModules (node:internal/modules/cjs/loader:1563:5)
    at loadPreloadModules (node:internal/process/pre_execution:730:5)
    at setupUserModules (node:internal/process/pre_execution:206:5)
    at prepareExecution (node:internal/process/pre_execution:159:5)
    at prepareMainThreadExecution (node:internal/process/pre_execution:54:10)
    at node:internal/main/run_main_module:11:19 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ 'internal/preload' ]
}

Node.js v20.15.1

    at genericNodeError (node:internal/errors:984:15)
    at wrappedFn (node:internal/errors:538:14)
    at ChildProcess.exithandler (node:child_process:422:12)
    at ChildProcess.emit (node:events:519:28)
    at ChildProcess.emit (node:domain:488:12)
    at maybeClose (node:internal/child_process:1105:16)
    at Socket.<anonymous> (node:internal/child_process:457:11)
    at Socket.emit (node:events:519:28)
    at Socket.emit (node:domain:488:12)
    at Pipe.<anonymous> (node:net:338:12)

The toggle does not seem to work for me :(

nickjanssen · 2024-11-18T06:02:47Z

This started to randomly happen to me after upgrading to Next 15. Disabling, restarting and then enabling the "javascript debugger" extension worked.

dBianchii · 2024-11-22T02:35:53Z

This started to randomly happen to me after upgrading to Next 15. Disabling, restarting and then enabling the "javascript debugger" extension worked.

Thank you!! awesome happened with me after upgrading to Next 15

AlmogCohen · 2025-01-08T13:04:10Z

This started to randomly happen to me after upgrading to Next 15. Disabling, restarting and then enabling the "javascript debugger" extension worked.

Thank you!! awesome happened with me after upgrading to Next 15

I didn't realize this due to the upgrade to Next 15 until you said it! Same solution worked.

thomasantony12 · 2025-01-22T07:41:10Z

I was using a remote SSH server to run the code and the error occurred to me. Following are the procedures which I used to resolve the problem.

Manually Check for bootloader.js

Check if the bootloader.js file exists in the mentioned path:

ls ~/.vscode-server/data/User/workspaceStorage/63314b8b92156532229f6a9bef0ab1d6/ms-vscode.js-debug/bootloader.js

If missing, manually reinstall the extension by clearing the cache:

rm -rf ~/.vscode-server/extensions
rm -rf ~/.vscode-server/data/User/workspaceStorage

Then reconnect using the Remote - SSH extension, which will reinstall all dependencies.

ahmedrowaihi · 2025-02-22T05:54:09Z

Methods:

method (1) : In VS Code/Cursor:
Press Cmd+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux)
Type debug.node.autoAttach
Select Debug: Toggle Auto Attach
Choose disabled
method (2) : add this to User preference JSON settings

 "debug.javascript.autoAttachFilter": "disabled",

connor4312 added the info-needed Issue requires more information from poster label Mar 3, 2020

connor4312 added this to the Backlog milestone Mar 6, 2020

connor4312 closed this as completed in 3056cb8 May 5, 2020

connor4312 added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels May 5, 2020

chasingSublimity mentioned this issue Jul 10, 2020

debug bootloader breaking vscode terminal microsoft/vscode#102063

Closed

Banou26 mentioned this issue Jul 12, 2020

Parcel 2: windows vscode 1.47 integrated terminal results in @parcel/workers: Cannot find module parcel-bundler/parcel#4880

Closed

chrmarti mentioned this issue Jan 15, 2021

Npm fails after 'Rebuild Container' microsoft/vscode-remote-release#4308

Closed

hotzevzl mentioned this issue Nov 2, 2023

disable autoAttachChildProcesses in the recommended vscode launch.json config Vizzuality/marxan-cloud#1570

Merged

samruddhikhandale mentioned this issue Mar 15, 2024

feature node: can't load bootsrap.js devcontainers/features#913

Open

nmgix mentioned this issue Mar 1, 2025

VSCode debugging error when using Yarn PnP with NextJS 15 vercel/next.js#72621

Open

Cannot find module bootloader.js #374

Cannot find module bootloader.js #374

Comments

jasonwilliams commented Mar 3, 2020

connor4312 commented Mar 3, 2020 • edited Loading

jasonwilliams commented Mar 3, 2020

connor4312 commented Mar 5, 2020

jasonwilliams commented Mar 5, 2020

connor4312 commented Mar 5, 2020

phyllisstein commented May 1, 2020 • edited Loading

connor4312 commented May 1, 2020

phyllisstein commented May 1, 2020

connor4312 commented May 1, 2020

jasonwilliams commented May 1, 2020

connor4312 commented May 1, 2020

connor4312 commented May 5, 2020 • edited Loading

paulsimongb commented Jul 9, 2020

connor4312 commented Jul 9, 2020

rossmc commented Jul 13, 2020 • edited Loading

ochicf commented Jul 13, 2020 • edited Loading

connor4312 commented Jul 13, 2020

mikeshot commented Jul 13, 2020 • edited Loading

amlcodes commented Jul 13, 2020 • edited Loading

connor4312 commented Jul 13, 2020

aventurella-honey commented Jul 14, 2020 • edited Loading

connor4312 commented Jul 14, 2020 • edited Loading

tehpsalmist commented Aug 17, 2020

connor4312 commented Aug 17, 2020 • edited Loading

tehpsalmist commented Aug 29, 2020

connor4312 commented Aug 29, 2020

tehpsalmist commented Aug 30, 2020

jeffbski-rga commented Sep 21, 2020

connor4312 commented Sep 21, 2020 • edited Loading

jeffbski-rga commented Sep 21, 2020

rayhatfield commented Oct 19, 2021

connor4312 commented Oct 19, 2021

rayhatfield commented Oct 19, 2021

Porges commented Jun 8, 2022

Porges commented Jun 8, 2022

JustinGrote commented Oct 25, 2022

RaviPabari commented Jan 19, 2023

louwers commented Aug 5, 2023 • edited Loading

shemy-gan commented May 29, 2024 • edited Loading

Austint30 commented Jul 1, 2024

lamuertepeluda commented Jul 19, 2024 • edited Loading

nickjanssen commented Nov 18, 2024

dBianchii commented Nov 22, 2024

AlmogCohen commented Jan 8, 2025

thomasantony12 commented Jan 22, 2025

Manually Check for bootloader.js

ahmedrowaihi commented Feb 22, 2025

connor4312 commented Mar 3, 2020 •

edited

Loading

phyllisstein commented May 1, 2020 •

edited

Loading

connor4312 commented May 5, 2020 •

edited

Loading

rossmc commented Jul 13, 2020 •

edited

Loading

ochicf commented Jul 13, 2020 •

edited

Loading

mikeshot commented Jul 13, 2020 •

edited

Loading

amlcodes commented Jul 13, 2020 •

edited

Loading

aventurella-honey commented Jul 14, 2020 •

edited

Loading

connor4312 commented Jul 14, 2020 •

edited

Loading

connor4312 commented Aug 17, 2020 •

edited

Loading

connor4312 commented Sep 21, 2020 •

edited

Loading

louwers commented Aug 5, 2023 •

edited

Loading

shemy-gan commented May 29, 2024 •

edited

Loading

lamuertepeluda commented Jul 19, 2024 •

edited

Loading