-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Open
Description
I get this issue and log when trying to deploy for the first time I guess when npm run build is ran? I have no idea how to fix or configure? Any ideas?
- 2026-02-09T20:25:14.511Z Initializing build environment...
- 2026-02-09T20:25:16.420Z Success: Finished initializing build environment
- 2026-02-09T20:25:16.825Z Cloning repository...
- 2026-02-09T20:25:18.173Z No build output detected to cache. Skipping.
- 2026-02-09T20:25:18.174Z No dependencies detected to cache. Skipping.
- 2026-02-09T20:25:18.175Z Detected the following tools from environment:
- 2026-02-09T20:25:18.335Z Executing user build command: npm run build
- 2026-02-09T20:25:19.836Z npm error code ENOENT
- 2026-02-09T20:25:19.836Z npm error syscall open
- 2026-02-09T20:25:19.837Z npm error path /opt/buildhome/repo/package.json
- 2026-02-09T20:25:19.837Z npm error errno -2
- 2026-02-09T20:25:19.837Z npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/opt/buildhome/repo/package.json'
- 2026-02-09T20:25:19.837Z npm error enoent This is related to npm not being able to find a file.
- 2026-02-09T20:25:19.837Z npm error enoent
- 2026-02-09T20:25:19.837Z npm error A complete log of this run can be found in: /opt/buildhome/.npm/_logs/2026-02-09T20_25_19_707Z-debug-0.log
- 2026-02-09T20:25:19.857Z Failed: error occurred while running build command
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels