Wrangler/Workerd crashes with no actionable output on hello world example #5083
Description
What versions & operating system are you using?
Inside the container
System:
OS: Linux 6.16 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
CPU: (2) x64 Common KVM processor
Memory: 1.87 GB / 3.82 GB
Container: Yes
Shell: 5.2.15 - /bin/bash
Binaries:
Node: 20.18.0 - /usr/local/bin/node
Yarn: 1.22.22 - /usr/local/bin/yarn
npm: 10.8.2 - /usr/local/bin/npm
pnpm: 9.15.9 - /app/node_modules/.bin/pnpm
npmPackages:
@cloudflare/workers-types: ^4.20241127.0 => 4.20250722.0
wrangler: ^4.5.1 => 4.25.1
Outside the container
I don't have node on the host, so here's a neofetch
OS: Arch Linux x86_64
Host: KVM/QEMU Standard PC (i440FX + PIIX, 1996) (pc-i440fx-9.0)
Kernel: Linux 6.16.5-arch1-1
Uptime: 1 day, 4 hours, 33 mins
Packages: 219 (pacman)
Shell: fish 4.0.2
Terminal: tmux 3.5a
CPU: Common KVM processor (2) @ 2.30 GHz
Memory: 1.85 GiB / 3.82 GiB (48%)
Swap: 511.78 MiB / 512.00 MiB (100%)
Disk (/): 9.31 GiB / 63.71 GiB (15%) - btrfs
Locale: en_US.UTF-8
Please provide a link to a minimal reproduction
https://developers.cloudflare.com/workers/get-started/quickstarts/
Describe the Bug
wrangler commands are failing in a brand new project with basically no error output. It appears to be any command that invokes workerd. The steps listed below succeed on my laptop, but fail on my server. My suspicion is that my server's CPU is responsible, as I already hit a feature set error with a prebuilt Caddy binary, but I don't know how I would verify this for wrangler. I would love any suggestions for commands that could give me more information to work with.
- I spin up a blank node container with
podman container run -it --rm docker.io/node bash - I run
npm create cloudflare@latest, which pulls 2.51.5 - I choose the template "Hello World example" with options "SSR / full-stack app" and "Typescript"
- The automatic
wrangler typescommand fails, as does what seems to be any command that tries to invoke workerd.
Sorry if this issue should be posted on the wrangler repository instead - I am just following the link that the CLI gave me.
Please provide any relevant error logs
Terminal output of npx wrangler types
root@4ab9267914fd:~/bitter-mud-9661# npx wrangler types
⛅️ wrangler 4.35.0
───────────────────
Generating project types...
declare namespace Cloudflare {
interface Env {
}
}
interface Env extends Cloudflare.Env {}
Generating runtime types...
service core:user:: Uncaught Error:
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.
If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose
✔ Would you like to report this error to Cloudflare? Wrangler's output and the error details will be shared with the Wrangler team to help us diagnose and fix the issue. … yes
🪵 Logs were written to "/root/.config/.wrangler/logs/wrangler-2025-09-11_02-50-26_415.log"
The mentioned log file
--- 2025-09-11T02:50:26.630Z debug
🪵 Writing logs to "/root/.config/.wrangler/logs/wrangler-2025-09-11_02-50-26_415.log"
---
--- 2025-09-11T02:50:26.629Z debug
Metrics dispatcher: Posting data {"deviceId":"1bd263e6-5a5d-472d-9dc0-083134c41808","event":"wrangler command started","timestamp":1757559026629,"properties":{"amplitude_session_id":1757559026626,"amplitude_event_id":0,"wranglerVersion":"4.35.0","osPlatform":"Linux","osVersion":"#1 SMP PREEMPT_DYNAMIC Thu, 04 Sep 2025 23:18:13 +0000","nodeVersion":24,"packageManager":"npm","isFirstUsage":false,"configFileType":"jsonc","isCI":false,"isPagesCI":false,"isWorkersCI":false,"isInteractive":true,"hasAssets":true,"argsUsed":[],"argsCombination":"","command":"wrangler types","args":{"envInterface":"<REDACTED>","includeRuntime":true,"includeEnv":true,"strictVars":true,"path":"worker-configuration.d.ts"}}}
---
--- 2025-09-11T02:50:26.643Z debug
.env file not found at "/root/bitter-mud-9661/.env". Continuing... For more details, refer to https://developers.cloudflare.com/workers/wrangler/system-environment-variables/
---
--- 2025-09-11T02:50:26.643Z debug
.env file not found at "/root/bitter-mud-9661/.env.local". Continuing... For more details, refer to https://developers.cloudflare.com/workers/wrangler/system-environment-variables/
---
--- 2025-09-11T02:50:26.678Z log
⛅️ wrangler 4.35.0
───────────────────
---
--- 2025-09-11T02:50:26.705Z log
Generating project types...
---
--- 2025-09-11T02:50:26.708Z debug
local dev variables file not found at ".dev.vars". Continuing... For more details, refer to https://developers.cloudflare.com/workers/wrangler/system-environment-variables/
---
--- 2025-09-11T02:50:26.708Z debug
.env file not found at "/root/bitter-mud-9661/.env". Continuing... For more details, refer to https://developers.cloudflare.com/workers/wrangler/system-environment-variables/
---
--- 2025-09-11T02:50:26.708Z debug
.env file not found at "/root/bitter-mud-9661/.env.local". Continuing... For more details, refer to https://developers.cloudflare.com/workers/wrangler/system-environment-variables/
---
--- 2025-09-11T02:50:26.711Z log
declare namespace Cloudflare {
interface Env {
}
}
interface Env extends Cloudflare.Env {}
---
--- 2025-09-11T02:50:26.711Z log
Generating runtime types...
---
--- 2025-09-11T02:50:28.817Z log
---
--- 2025-09-11T02:50:28.879Z error
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.
---
--- 2025-09-11T02:50:28.898Z debug
MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
at #assembleAndUpdateConfig (/root/bitter-mud-9661/node_modules/miniflare/dist/src/index.js:61621:13)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Mutex.runWith (/root/bitter-mud-9661/node_modules/miniflare/dist/src/index.js:38853:48)
at async #waitForReady (/root/bitter-mud-9661/node_modules/miniflare/dist/src/index.js:61708:5)
at async _Miniflare.dispatchFetch (/root/bitter-mud-9661/node_modules/miniflare/dist/src/index.js:61879:5)
at async generate (/root/bitter-mud-9661/node_modules/wrangler/wrangler-dist/cli.js:148975:17)
at async generateRuntimeTypes (/root/bitter-mud-9661/node_modules/wrangler/wrangler-dist/cli.js:148952:18)
at async Object.handler (/root/bitter-mud-9661/node_modules/wrangler/wrangler-dist/cli.js:149660:51)
at async Object.handler (/root/bitter-mud-9661/node_modules/wrangler/wrangler-dist/cli.js:84893:7)
---
--- 2025-09-11T02:50:28.899Z log
If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose
---
--- 2025-09-11T02:51:09.185Z debug
Sentry: Capturing exception MiniflareCoreError [ERR_RUNTIME_FAILURE]: The Workers runtime failed to start. There is likely additional logging output above.
---
--- 2025-09-11T02:51:09.192Z debug
Metrics dispatcher: Posting data {"deviceId":"1bd263e6-5a5d-472d-9dc0-083134c41808","event":"wrangler command errored","timestamp":1757559069192,"properties":{"amplitude_session_id":1757559026626,"amplitude_event_id":1,"wranglerVersion":"4.35.0","osPlatform":"Linux","osVersion":"#1 SMP PREEMPT_DYNAMIC Thu, 04 Sep 2025 23:18:13 +0000","nodeVersion":24,"packageManager":"npm","isFirstUsage":false,"configFileType":"jsonc","isCI":false,"isPagesCI":false,"isWorkersCI":false,"isInteractive":true,"hasAssets":true,"argsUsed":[],"argsCombination":"","command":"wrangler types","args":{"envInterface":"<REDACTED>","includeRuntime":true,"includeEnv":true,"strictVars":true,"path":"worker-configuration.d.ts"},"durationMs":42594,"durationSeconds":42.594,"durationMinutes":0.7099,"errorType":"MiniflareCoreError"}}
---
Extra
I confirmed via hacking around in node_modules that service core:user:: Uncaught Error: is the output of workerd