🐛 BUG: VSCode debugger doesn't work on Wrangler 3.19 and up

[wikes82]

Which Cloudflare product(s) does this pertain to?

Wrangler core

What version(s) of the tool(s) are you using?

Wrangler 3.19.0

What version of Node are you using?

20.11.1

What operating system and version are you using?

Windows

Describe the Bug

Observed behavior

VSCode debug doesn't work anymore since Wrangler 3.19
The breakpoint is hit, but it continue executing instead of pausing the execution.

Expected behavior

Make VSCode debug work again.

Steps to reproduce

Please provide the following:

Please provide a link to a minimal reproduction

No response

Please provide any relevant error logs

No response

[ad6025b]

@mrbbot @can someone please look at this? the vscode step debugger has been broken since >3.19

[mrbbot]

/cc @admah

[wikes82]

Just an update, on my original submission only tested on Windows.
I have tested on Linux and macOS as well, and it's also broken.

[ad6025b]

@mrbbot @admah this refactoring https://github.com/cloudflare/workers-sdk/releases/tag/wrangler%403.19.0

==> this is the commit that broke the vscode step debugger
==> this commit: 29df8e1

[ad6025b]

@mrbbot @admah Ok, i narrowed to the same reported problem here:
==> this is the issue: cloudflare/workerd#2051

the only workaround is to downgrade to v3.18. (3.19 and above is all broken)

running the command [ npx wrangler dev --log-level debug ]
you can see the error:

workerd/jsg/util.c++:291: error: e = kj/compat/http.c++:5754: failed: WebSocket protocol error; protocolError.statusCode = 1009; protocolError.description = Message is too large: 4670082 > 1048576

---

other people have report same problem here on discord:
https://discord.com/channels/595317990191398933/799437470004412476/1219640695296360513

[kyle-pena-nlp]

Hey devs - you kind of need to fix this. The debugger doesn't work for codebases over a certain (but still reasonable size). That means any of the work you've done past 3.18 isn't usable to anybody who needs a debugger. Please prioritize accordingly.

[RamIdeas]

We have a fix in-progress for this in workerd cloudflare/workerd#2164

Once that lands, we will make wrangler set that flag when running workerd, which should fix this issue