React/ Next failure - my app is not deploying anymore

General
1

since the time i started to have this security alert

) Security Check Recommended (CVE-2025-55182): Please review your application’s dependencies. If you are running React or Next.js applications, immediately update to the latest stable versions (React 19.2.1 or the relevant version of Next.js), and redeploy. ) ,

my app stopped deploying and gives error each time i try to publish

i tried to upgrade next by adding this order to my terminal using the prototyper

“npx fix-react2shell-next”

but the whole app stopped working , so i reverted to the older version

but now im stuck and cant publish my app anymore , and keeps getting error no matter what i did

any help is appreciated

2

You have no choice to update to secure versions of React/Next. I am sorry that this happens, it also happened to me and it was just resolved. So, updating through the npx command and then fixing the errors that appear thanks to the Prototyper is the way. Remember to look at the error logs.

My situation:

3

here is the bulid log i get

  • BUILD source: Firebase System Finished Step #2 - “preparer” Starting Step #3 - “pack” Pulling image: gcr.io/k8s-skaffold/pack Using default tag: latest latest: Pulling from k8s-skaffold/pack 396c31837116: Pulling fs layer 9776b10d5c8c: Pulling fs layer 52cb9ac3197f: Pulling fs layer 9776b10d5c8c: Verifying Checksum 9776b10d5c8c: Download complete 396c31837116: Verifying Checksum 396c31837116: Download complete 52cb9ac3197f: Verifying Checksum 52cb9ac3197f: Download complete 396c31837116: Pull complete 9776b10d5c8c: Pull complete 52cb9ac3197f: Pull complete Digest: sha256:221c0c0d9a90f46f108bb888a1da9e99c82ff631e8b1c63b0223ea951752bd53 Status: Downloaded newer image for gcr.io/k8s-skaffold/pack:latest gcr.io/k8s-skaffold/pack:latest nodejs_20251202_RC00: Pulling from serverless-runtimes/google-22-full/builder/nodejs Digest: sha256:4dba69b6f28e0bcbb5ac16874a287ab9299367e002e11a6c0eda1ef76fefbdd2 Status: Image is up to date for us-central1-docker.pkg.dev/serverless-runtimes/google-22-full/builder/nodejs:nodejs_20251202_RC00 public-image-next: Pulling from serverless-runtimes/google-22/run/base 63e5bc7682b8: Already exists 7c24c26cea09: Pulling fs layer ba2668403dd2: Pulling fs layer 7c24c26cea09: Verifying Checksum 7c24c26cea09: Download complete ba2668403dd2: Verifying Checksum ba2668403dd2: Download complete 7c24c26cea09: Pull complete ba2668403dd2: Pull complete Digest: sha256:08f6f2356c8d4928a2520b23589420a360945c62e5654a7eed9e19a959c74404 Status: Downloaded newer image for us-central1-docker.pkg.dev/serverless-runtimes/google-22/run/base:public-image-next ===> ANALYZING Image with name “us-central1-docker.pkg.dev/lami-clinic/firebaseapphosting-images/studio:a-omzaxc4s9bys” not found ===> DETECTING target distro name/version labels not found, reading /etc/os-release file 4 of 6 buildpacks participating google.nodejs.runtime 1.0.0 google.nodejs.firebasenextjs 0.0.1 google.nodejs.npm 1.1.0 google.nodejs.firebasebundle 0.0.1 ===> RESTORING ===> BUILDING target distro name/version labels not found, reading /etc/os-release file === Node.js - Runtime (google.nodejs.runtime@1.0.0) === Nodejs version not specified, using the latest available Nodejs runtime for the stack “ubuntu2204” 2025/12/08 18:04:37 [DEBUG] GET https://dl.google.com/runtimes/ubuntu2204/nodejs/version.json Adding image label google.runtime-version: nodejs22 2025/12/08 18:04:38 [DEBUG] GET https://dl.google.com/runtimes/ubuntu2204/nodejs/version.json Installing Node.js v22.21.0. 2025/12/08 18:04:39 [DEBUG] GET https://dl.google.com/runtimes/ubuntu2204/nodejs/nodejs-22.21.0.tar.gz Installing the heapsize.sh exec.d script. === Node.js - Firebasenextjs (google.nodejs.firebasenextjs@0.0.1) === ***** CACHE MISS: “npm_modules” Installing nextjs adaptor 14.0.21 === Node.js - Npm (google.nodejs.npm@1.1.0) === ***** CACHE MISS: “npm_modules” Installing application dependencies.

failed to build: (error ID: 7fa33aaa): npm error code ERESOLVE npm error ERESOLVE could not resolve npm error npm error While reso@genkit-aiving: @genkit-ai/next@1.4.0 npm error @genkit-aiound: next@14.2.5 npm error node_modules/next npm error next@“14.2.5” from the root project npm error npm error Could not resolve dependency: npm error peer next@genkit-ai“^15.0.0” from @genkit-ai/next@1.4.0 npm err@genkit-air @genkit-aiode_@genkit-aiodules/@genkit-ai/next npm error @genkit-ai/next@genkit-ai“1.4.0” from the@genkit-airoot project npm error npm error Conflicting peer dependency: next@15.5.7 npm error node_modul@genkit-ais/next npm error peer next@“^15.0.0@genkit-ai from @genkit-ai/next@1.4@genkit-ai0 npm error @genkit-aiode_modules/@genkit-ai/next npm error @genkit-ai/next@genkit-ai“1.4.0” from the@genkit-airoot project npm error npm error Fix the upstream dependency conflict, or retry npm error this command with --force or --legacy-peer-deps npm error to accept an incorrect (and potentially broken) dependency resolution. npm error npm error npm error For a full report see: npm error /www-data-home/.npm/_logs/2025-12-08T18_04_49_446Z-eresolve-report.txt npm error A complete log of this run can be found in: /www-data-home/.npm/_logs/2025-12-08T18_04_49_446Z-debug-0.log ERROR: failed to build: exit status 1 ERROR: failed to build: executing lifecycle: failed with status code: 51 Finished Step #3 - “pack” ERROR ERROR: build step 3 “gcr.io/k8s-skaffold/pack” failed: step exited with non-zero status: 1

4

Does npm install && npm run build succeed locally?

5

yes , when i added the order to terminal i got it succeeded

6

I am writing to report a significant issue I’ve encountered since my development environment was upgraded from Next.js version 15.3.3 to 15.3.6.

Since the update, my application has been stuck in a continuous loop of build errors. Although we have attempted to fix numerous issues sequentially (including type errors, dependency inconsistencies, and Firebase SDK problems), each fix seems to uncover a new underlying problem, making the adjustment process unfeasible.

The hosting build process, which is quite strict, is now blocking the deployment of features that were previously working perfectly on version 15.3.3. Given the extensive number of adjustments required and the complexity of the errors that have arisen, migrating to version 15.3.6 has become a roadblock to my project’s progress.

I would like to inquire if there is any plan to support version 15.3.3 of Next.js again in the hosting environment, or if there is any way to revert my project to this version, which was stable and functional for my application.

Thank you for your attention. I look forward to your response.

Sincerely,

7

i solved the issue , main problem was im migrating to wrong version number of next , and everything is ok