CD
Cloudflare Developers•2w ago
Juan

npm error A complete log of this run can be found in: /opt/buildhome/.npm/_logs/...

My application started to drop this error on any build, even retrying old deployments gets thesame error. This waas working a few days ago. I've changed nothing on the project settings or the code, simply tried to re-deploy preview and production builds that worked before and now I get this error. 
23:21:58.824    Installing project dependencies: npm install --progress=false
23:22:20.950    npm error A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-04-09T02_21_59_147Z-debug-0.log
23:22:20.981    Error: Exit with error code: 1
23:22:20.982        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
23:22:20.982        at Object.onceWrapper (node:events:652:26)
23:22:20.982        at ChildProcess.emit (node:events:537:28)
23:22:20.982        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
23:22:20.993    Failed: build command exited with code: 1
23:22:22.476    Failed: error occurred while running build command
23:21:58.824    Installing project dependencies: npm install --progress=false
23:22:20.950    npm error A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-04-09T02_21_59_147Z-debug-0.log
23:22:20.981    Error: Exit with error code: 1
23:22:20.982        at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
23:22:20.982        at Object.onceWrapper (node:events:652:26)
23:22:20.982        at ChildProcess.emit (node:events:537:28)
23:22:20.982        at ChildProcess._handle.onexit (node:internal/child_process:291:12)
23:22:20.993    Failed: build command exited with code: 1
23:22:22.476    Failed: error occurred while running build command
No idea how can I get to that log file to check what's wrong. It's a Sveltekit project using Claoudflare Pages. Anyone having the same issue? Thanks.
1 Reply
Juan
JuanOP•2w ago
Application started to build again. Only thing I can think, the problem was a dependency that was broken on a patch version, and then fixed recently. But, not having access to the log to see what was the issue was scary.

Did you find this page helpful?