i just placed a correctly configured `package-lock.json` in my github thing and now i get this
======== Output: paketo-buildpacks/node-run-script@0.4.3 ========
expected script(s) build from $BP_NODE_RUN_SCRIPTS to exist in package.json
err: paketo-buildpacks/node-run-script@0.4.3 (1)
======== Output: paketo-buildpacks/node-run-script@0.4.3 ========
expected script(s) build from $BP_NODE_RUN_SCRIPTS to exist in package.json
err: paketo-buildpacks/node-run-script@0.4.3 (1)
======== Output: paketo-buildpacks/node-run-script@0.4.3 ========
expected script(s) build from $BP_NODE_RUN_SCRIPTS to exist in package.json
err: paketo-buildpacks/node-run-script@0.4.3 (1)
======== Output: paketo-buildpacks/node-run-script@0.5.0 ========
could not find script(s) [build] in package.json
err: paketo-buildpacks/node-run-script@0.5.0 (1)
======== Output: paketo-buildpacks/node-run-script@0.5.0 ========
could not find script(s) [build] in package.json
err: paketo-buildpacks/node-run-script@0.5.0 (1)
6 of 12 buildpacks participating
paketo-buildpacks/ca-certificates 3.4.0
paketo-buildpacks/node-engine 0.17.1
paketo-buildpacks/npm-install 0.10.7
paketo-buildpacks/node-module-bom 0.4.3
paketo-buildpacks/node-start 0.8.5
paketo-buildpacks/npm-start 0.10.2
===> RESTORING
======== Output: paketo-buildpacks/node-run-script@0.4.3 ========
expected script(s) build from $BP_NODE_RUN_SCRIPTS to exist in package.json
err: paketo-buildpacks/node-run-script@0.4.3 (1)
======== Output: paketo-buildpacks/node-run-script@0.4.3 ========
expected script(s) build from $BP_NODE_RUN_SCRIPTS to exist in package.json
err: paketo-buildpacks/node-run-script@0.4.3 (1)
======== Output: paketo-buildpacks/node-run-script@0.4.3 ========
expected script(s) build from $BP_NODE_RUN_SCRIPTS to exist in package.json
err: paketo-buildpacks/node-run-script@0.4.3 (1)
======== Output: paketo-buildpacks/node-run-script@0.5.0 ========
could not find script(s) [build] in package.json
err: paketo-buildpacks/node-run-script@0.5.0 (1)
======== Output: paketo-buildpacks/node-run-script@0.5.0 ========
could not find script(s) [build] in package.json
err: paketo-buildpacks/node-run-script@0.5.0 (1)
6 of 12 buildpacks participating
paketo-buildpacks/ca-certificates 3.4.0
paketo-buildpacks/node-engine 0.17.1
paketo-buildpacks/npm-install 0.10.7
paketo-buildpacks/node-module-bom 0.4.3
paketo-buildpacks/node-start 0.8.5
paketo-buildpacks/npm-start 0.10.2
===> RESTORING
could not find script(s) [build] in package.json? never seen that before3 Replies
i had to fix something and i just got this error
im switching
ERROR: failed to export: get run image top layer SHA: image "us-west1-docker.pkg.dev/railway-infra/railway-docker-users/project/d9cf893f-1e36-4c00-a07c-24ee7ad06dde/service/54ecf624-0eb7-4b27-b11a-61aa79462e38:e90a541b-ab81-4a3d-bc4b-fcd403dfc943" has no layers
ERROR: failed to build: executing lifecycle: failed with status code: 62
ERROR: failed to export: get run image top layer SHA: image "us-west1-docker.pkg.dev/railway-infra/railway-docker-users/project/d9cf893f-1e36-4c00-a07c-24ee7ad06dde/service/54ecf624-0eb7-4b27-b11a-61aa79462e38:e90a541b-ab81-4a3d-bc4b-fcd403dfc943" has no layers
ERROR: failed to build: executing lifecycle: failed with status code: 62
buildpacksWe don’t support Heroku buildpacks anymore
Or Paketo
ok
so ive switched and now i dont have that problem
ty