cloudflare / cloudflare/workerd
code: ENONT when trying to run wrangler, even with `npm i`
- Dominant language
- C++
- Stars
- 8.7k
- Forks
- 739
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 174
Description
### Which Cloudflare product(s) does this pertain to?
Wrangler
### What versions & operating system are you using?
Linux 6.14.5, Guix
### Please provide a link to a minimal reproduction
_No response_
### Describe the Bug
On a new project, running wrangler results in `workerd ENONT` error after running `npm run dev`. Running `wrangler deploy` works without issue. This seems to just happen specifically on the `wrangler dev` and `wrangler types` commands.
### Please provide any relevant error logs
```
$ npm run dev
> my-first-worker@0.0.0 dev
> wrangler dev
⛅️ wrangler 4.14.4
-------------------
No bindings found.
❓ Your types might be out of date. Re-run `wrangler types` to ensure your types are correct.
Error: spawn /home/me/backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:285:19)
at onErrorNT (node:internal/child_process:483:16)
at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn /home/me/backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd',
path: '/home/me/backend/node_modules/@cloudflare/workerd-linux-64/bin/workerd',
spawnargs: [
'serve',
'--binary',
'--experimental',
'--socket-addr=entry=localhost:8787',
'--external-addr=loopback=localhost:45613',
'--control-fd=3',
'-'
]
}
```
Contributor guide
Assessment
This issue has not been assessed yet.