-
Notifications
You must be signed in to change notification settings - Fork 10.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Koyeb deployment error #293
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Build ready to start▶️
HEAD is now at 8d13427 Suhail 1.3.0
Previous image with name "registry01.prod.koyeb.com/k-f763bd8e-fbe1-4c4a-829e-5a6fb73fbb55/6c7ba4a0-097c-4005-8e4e-be5583dbea32:latest" not found
3 of 5 buildpacks participating
heroku/nodejs-engine 2.6.2
heroku/nodejs-npm-install 2.6.2
heroku/procfile 2.0.2
Layer cache not found
[Heroku Node.js Engine Buildpack]
[Checking Node.js version]
Node.js version not specified, using 20.x
Resolved Node.js version: 20.10.0
[Installing Node.js distribution]
Downloading Node.js 20.10.0
Extracting Node.js 20.10.0
Installing Node.js 20.10.0
Heroku Node.js npm Install Buildpack
! Couldn't determine Node.js package manager. Package manager lockfile not found.
!
! A lockfile from a supported package manager is required to install Node.js dependencies. The package.json for this project specifies dependencies, but there isn't a lockfile.
!
! To use npm to install dependencies, run
npm install
. This command will generate apackage-lock.json
lockfile.!
! Or, to use yarn to install dependencies, run
yarn install
. This command will generate ayarn.lock
lockfile.!
! Or, to use pnpm to install dependencies, run
pnpm install
. This command will generate apnpm-lock.yaml
lockfile.!
! Ensure the resulting lockfile is committed to the repository, then try again.
ERROR: failed to build: exit status 1
exit status 51
The text was updated successfully, but these errors were encountered: