Wrangler Pages Dev Unresponsive after Node.js Crashes

Whenever Node.js crashes from a syntax error or throws an error, wrangler doesn't want to start the local server at all. All I get is this error after running npx wrangler pages dev dist:
[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-09-04",
but you've requested "2023-09-13". Falling back to "2023-09-04"...
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
[mf:wrn] The latest compatibility date supported by the installed Cloudflare Workers Runtime is "2023-09-04",
but you've requested "2023-09-13". Falling back to "2023-09-04"...
✘ [ERROR] MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
I am currently developing a react app, the only way I can solve this issue is by restarting my laptop. Has anybody solved / encountered this issue? Any help would be appreciated!
1 Reply
IanVS
IanVS15mo ago
I hit this regularly as well. I'd also love to know how it can be resolved OK I found a way to reset it. ps -ax | grep 8788 gives me the process that is still running:
48739 ttys002 0:00.06 /Users/ianvs/.npm/_npx/32026684e21afda6/node_modules/@cloudflare/workerd-darwin-arm64/bin/workerd serve --binary --experimental --socket-addr=entry=0.0.0.0:8788 --external-addr=loopback=localhost:61484 --control-fd=3 - --inspector-addr=localhost:61481
48739 ttys002 0:00.06 /Users/ianvs/.npm/_npx/32026684e21afda6/node_modules/@cloudflare/workerd-darwin-arm64/bin/workerd serve --binary --experimental --socket-addr=entry=0.0.0.0:8788 --external-addr=loopback=localhost:61484 --control-fd=3 - --inspector-addr=localhost:61481
You'd need to replace the 8788 with whatever port your hung process started up with. Or you could try grepping for workerd instead, maybe
Want results from more Discord servers?
Add your server