Cloudflare build error
Unanswered
Sikqo (Termed) posted this in #help-forum
hello i need help with build i dont know why i cant finsh the build without error
2025-02-21T20:42:11.517214Z Cloning repository...
2025-02-21T20:42:12.198125Z From https://github.com/xxxx
2025-02-21T20:42:12.19857Z * branch 91a6c0f03ea5d141b1d33d14e7080442cb380091 -> FETCH_HEAD
2025-02-21T20:42:12.198709Z
2025-02-21T20:42:12.232234Z HEAD is now at 91a6c0f Add files via upload
2025-02-21T20:42:12.232688Z
2025-02-21T20:42:12.313276Z
2025-02-21T20:42:12.313876Z Using v2 root directory strategy
2025-02-21T20:42:12.335162Z Success: Finished cloning repository files
2025-02-21T20:42:13.909964Z Checking for configuration in a Wrangler configuration file (BETA)
2025-02-21T20:42:13.910493Z
2025-02-21T20:42:15.013864Z No wrangler.toml file found. Continuing.
2025-02-21T20:42:15.093088Z Detected the following tools from environment: nodejs@18.20.4
2025-02-21T20:42:15.093681Z Installing nodejs 18.20.4
2025-02-21T20:42:15.982457Z Trying to update node-build... ok
2025-02-21T20:42:16.080592Z To follow progress, use 'tail -f /tmp/node-build.20250221204216.490.log' or pass --verbose
2025-02-21T20:42:16.183661Z Downloading node-v18.20.4-linux-x64.tar.gz...
2025-02-21T20:42:16.412454Z -> https://nodejs.org/dist/v18.20.4/node-v18.20.4-linux-x64.tar.gz
2025-02-21T20:42:17.92938Z
2025-02-21T20:42:17.929727Z WARNING: node-v18.20.4-linux-x64 is in LTS Maintenance mode and nearing its end of life.
2025-02-21T20:42:17.929912Z It only receives critical security updates, critical bug fixes and documentation updates.
2025-02-21T20:42:17.930083Z
2025-02-21T20:42:17.930193Z Installing node-v18.20.4-linux-x64...
2025-02-21T20:42:18.313146Z Installed node-v18.20.4-linux-x64 to /opt/buildhome/.asdf/installs/nodejs/18.20.4
2025-02-21T20:42:18.313435Z
2025-02-21T20:42:11.517214Z Cloning repository...
2025-02-21T20:42:12.198125Z From https://github.com/xxxx
2025-02-21T20:42:12.19857Z * branch 91a6c0f03ea5d141b1d33d14e7080442cb380091 -> FETCH_HEAD
2025-02-21T20:42:12.198709Z
2025-02-21T20:42:12.232234Z HEAD is now at 91a6c0f Add files via upload
2025-02-21T20:42:12.232688Z
2025-02-21T20:42:12.313276Z
2025-02-21T20:42:12.313876Z Using v2 root directory strategy
2025-02-21T20:42:12.335162Z Success: Finished cloning repository files
2025-02-21T20:42:13.909964Z Checking for configuration in a Wrangler configuration file (BETA)
2025-02-21T20:42:13.910493Z
2025-02-21T20:42:15.013864Z No wrangler.toml file found. Continuing.
2025-02-21T20:42:15.093088Z Detected the following tools from environment: nodejs@18.20.4
2025-02-21T20:42:15.093681Z Installing nodejs 18.20.4
2025-02-21T20:42:15.982457Z Trying to update node-build... ok
2025-02-21T20:42:16.080592Z To follow progress, use 'tail -f /tmp/node-build.20250221204216.490.log' or pass --verbose
2025-02-21T20:42:16.183661Z Downloading node-v18.20.4-linux-x64.tar.gz...
2025-02-21T20:42:16.412454Z -> https://nodejs.org/dist/v18.20.4/node-v18.20.4-linux-x64.tar.gz
2025-02-21T20:42:17.92938Z
2025-02-21T20:42:17.929727Z WARNING: node-v18.20.4-linux-x64 is in LTS Maintenance mode and nearing its end of life.
2025-02-21T20:42:17.929912Z It only receives critical security updates, critical bug fixes and documentation updates.
2025-02-21T20:42:17.930083Z
2025-02-21T20:42:17.930193Z Installing node-v18.20.4-linux-x64...
2025-02-21T20:42:18.313146Z Installed node-v18.20.4-linux-x64 to /opt/buildhome/.asdf/installs/nodejs/18.20.4
2025-02-21T20:42:18.313435Z
6 Replies
2025-02-21T20:42:19.338344Z Executing user command: npm install && npm run build
2025-02-21T20:42:20.06631Z npm error code ENOENT
2025-02-21T20:42:20.066821Z npm error syscall open
2025-02-21T20:42:20.066999Z npm error path /opt/buildhome/repo/package.json
2025-02-21T20:42:20.067115Z npm error errno -2
2025-02-21T20:42:20.067503Z npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/opt/buildhome/repo/package.json'
2025-02-21T20:42:20.067941Z npm error enoent This is related to npm not being able to find a file.
2025-02-21T20:42:20.068077Z npm error enoent
2025-02-21T20:42:20.068715Z
2025-02-21T20:42:20.06897Z npm error A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-02-21T20_42_19_668Z-debug-0.log
2025-02-21T20:42:20.07572Z Failed: Error while executing user command. Exited with error code: 254
2025-02-21T20:42:20.085524Z Failed: build command exited with code: 1
2025-02-21T20:42:21.277281Z Failed: error occurred while running build command
2025-02-21T20:42:20.06631Z npm error code ENOENT
2025-02-21T20:42:20.066821Z npm error syscall open
2025-02-21T20:42:20.066999Z npm error path /opt/buildhome/repo/package.json
2025-02-21T20:42:20.067115Z npm error errno -2
2025-02-21T20:42:20.067503Z npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/opt/buildhome/repo/package.json'
2025-02-21T20:42:20.067941Z npm error enoent This is related to npm not being able to find a file.
2025-02-21T20:42:20.068077Z npm error enoent
2025-02-21T20:42:20.068715Z
2025-02-21T20:42:20.06897Z npm error A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2025-02-21T20_42_19_668Z-debug-0.log
2025-02-21T20:42:20.07572Z Failed: Error while executing user command. Exited with error code: 254
2025-02-21T20:42:20.085524Z Failed: build command exited with code: 1
2025-02-21T20:42:21.277281Z Failed: error occurred while running build command
this is all
need someone who can help me
🙏
@Sikqo (Termed) need someone who can help me
are you using a monorepo?
the error states thatat
repo/package.json doesn't exist