-
Notifications
You must be signed in to change notification settings - Fork 952
Description
What versions & operating system are you using?
System:
OS: Linux 6.6 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-13620H
Memory: 9.12 GB / 15.50 GB
Container: Yes
Shell: 5.8.1 - /usr/bin/zsh
Binaries:
Node: 23.11.0 - ~/.nvm/versions/node/v23.11.0/bin/node
npm: 10.9.2 - ~/.nvm/versions/node/v23.11.0/bin/npm
pnpm: 10.12.2 - ~/.local/share/pnpm/pnpm
npmPackages:
@cloudflare/vitest-pool-workers: ^0.8.19 => 0.8.64
wrangler: ^4.30.0 => 4.30.0
Note: This setup is Windows 11 running Ubuntu in WSL2. VSCode is installed in Windows, and all dev tooling, including Node, Wrangler, etc, are in a WSL2 folder. This has been a solid environment for many years. I have also tested on a Core i5 Asus Chromebook in developer mode using Google's official Debian VM, also solid for several years, and it too exhibits the same new behaviour.
Please provide a link to a minimal reproduction
No link but the following steps will help
- Run
npx wrangler init new-debug-test
Hello World example
Worker only
JavaScript
No
No
- Set a breakpoint in the
src/index.js
file
Describe the Bug
Before Wrangler 4.23, I was using VSCode debugging extensively without issue. From 4.23 onward, debugging no longer works in VSCode.
Downgrading to anything < 4.23 consistently works, and upgrading to anything => 4.23 consistently does not.
The debugger appears to attach if I use a launch config, but breakpoints are not hit. If I skip the launch config and run in a JavaScript Debug Terminal, then the debugger appears to connect, in that I have a session badge on the Run and Debug icon in the left sidebar, but breakpoints are grey circles, not red, and breakpoints are not hit.
If I configure my breakpoints panel to break on Caught Exceptions then it breaks on throw new TypeError(
${JSON.stringify(workerName)} worker not found);
on line 60606 of node_modules/miniflare/dist/src/index.js
Please provide any relevant error logs
Exception has occurred: TypeError: "InspectorProxyWorker" worker not found
at #findAndAssertWorkerIndex (/home/tforster/TroyForster/abc/new-debug-test/node_modules/miniflare/dist/src/index.js:60606:15)
at _Miniflare.unsafeGetDirectURL (/home/tforster/TroyForster/abc/new-debug-test/node_modules/miniflare/dist/src/index.js:60490:55)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async ProxyController.reconnectInspectorProxyWorker (/home/tforster/TroyForster/abc/new-debug-test/node_modules/wrangler/wrangler-dist/cli.js:178640:43)
at async ProxyController.sendMessageToInspectorProxyWorker (/home/tforster/TroyForster/abc/new-debug-test/node_modules/wrangler/wrangler-dist/cli.js:178723:29)
Metadata
Metadata
Assignees
Labels
Type
Projects
Status