donpui
commented
3 months ago I have exactly the same issue. Also tried pack locally, get also the same issue:
pack build --builder=gcr.io/buildpacks/firebase-app-hosting-22/builder:latest <project>
builder] Running "npm ci --quiet (NODE_ENV=development)"
[builder] npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
[builder] npm warn deprecated npmlog@5.0.1: This package is no longer supported.
[builder] npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
[builder] npm warn deprecated gauge@3.0.2: This package is no longer supported.
[builder] npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported.
[builder] npm warn deprecated @humanwhocodes/object-schema@2.0.3: Use @eslint/object-schema instead
[builder] npm warn deprecated @humanwhocodes/config-array@0.11.14: Use @eslint/config-array instead
[builder] npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
[builder]
[builder] added 579 packages, and audited 580 packages in 35s
[builder]
[builder] 147 packages are looking for funding
[builder] run `npm fund` for details
[builder]
[builder] found 0 vulnerabilities
[builder] Done "npm ci --quiet (NODE_ENV=development)" (35.019103975s)
[builder] --------------------------------------------------------------------------------
[builder] Running "npm exec --prefix /layers/google.nodejs.firebasenextjs/npm_modules apphosting-adapter-nextjs-build"
[builder] Done "npm exec --prefix /layers/google.nodejs.firebasenextjs/npm_m..." (1m12.641180659s)
[builder] --------------------------------------------------------------------------------
[builder] Running "npm prune --production"
[builder] npm warn config production Use `--omit=dev` instead.
[builder]
[builder] up to date, audited 267 packages in 2s
[builder]
[builder] 19 packages are looking for funding
[builder] run `npm fund` for details
[builder]
[builder] found 0 vulnerabilities
[builder] Done "npm prune --production" (2.002502209s)
[builder] === Node.js - Firebasebundle (google.nodejs.firebasebundle@0.0.1) ===
[builder] --------------------------------------------------------------------------------
[builder] failed to build: (error ID: 6fa8e297):
[builder] looking up output bundle env FIREBASE_OUTPUT_BUNDLE_DIR
[builder] --------------------------------------------------------------------------------
[builder] Sorry your project couldn't be built.
[builder] Our documentation explains ways to configure Buildpacks to better recognise your project:
[builder] -> https://cloud.google.com/docs/buildpacks/overview
[builder] If you think you've found an issue, please report it:
[builder] -> https://github.com/GoogleCloudPlatform/buildpacks/issues/new
[builder] --------------------------------------------------------------------------------
[builder] Timer: Builder ran for 2m7.854129725s and ended at 2024-08-05T08:33:45Z
[builder] ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle: failed with status code: 51
zuldy
dorraba
Yuangwang
llwire
connershoop
Describe the bug
Deploys for NextJS backends are failing due to the recent version update in the NextJS apphosting adapter.
After combing through the logs for my last successful deploy and the first failing deploy, I noticed that the only difference was that the
@apphosting/adapter-nextjsversion was bumped up to version14.0.5in the failing case. I believe this is the cause of the issues. All of my failing deploy install and try to run14.0.5.Those two deploys were just over an hour apart and the only change between the two commits a text change, so it would not affect deploys.
Additional context How are you using GCP buildpacks?
packand thegcr.io/buildpacks/builderDid this used to work? Yes, it used to work.
The last working deploy and first failing deploy were 1hr and 10mins apart, with no breaking code changes.
What language is your project primarily written in? Node.js
Steps To Reproduce Steps to reproduce the behavior:
Expected behavior The app to deploy.
Actual behavior ERROR: failed to build: exit status 1 ERROR: failed to build: executing lifecycle: failed with status code: 51
Success Log Snippet
Failure Log Snippet