Hi,

Can you share your vercel.json and package.json file? If you are using monorepo, please share your root vercel.json as well.

First, I want to try to get you unstuck as quickly as possible with a temporary workaround. You may be able to deploy from local build with the --prebuilt flag.

As @swarnava mentioned, the vercel.json and package.json would tell us more about the configuration settings for the project.

You're already getting help from the very best, but wanted to say - hi @mikenikles! Nice to see you here

We don't have a vercel.json file. As for the root-level and packages/webapp package.json files, is there anything other than what I share that you need?

Our GitHub workflow step to deploy the web app is:

1
  deploy-webapp-dev:
2
    runs-on: ubuntu-latest
3

4
    environment:
5
      name: webapp-dev
6
      url: https://dev.redacted.com
7

8
    defaults:
9
      run:
10
        working-directory: .
11

12
    steps:
13
      - uses: actions/checkout@v4
14

15
      # using a fork of amondnet/vercel-action for now until it is updated for node20
16
      - uses: vincent8balls/vercel-action@master
17
        with:
18
          vercel-token: ${{ secrets.VERCEL_TOKEN }} # Required
19
          vercel-org-id: ${{ secrets.VERCEL_ORG_ID}} #Required
20
          vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID}} #Required
21
          scope: <redacted>
22
          vercel-project-name: webapp

The support ticket (#311491) contains a link to one of the deployments that failed in case that provides more context. The specific deployment is 6oem3zGWUR8tZebqUDhriR66y9A9

Hi Pauline !

Yes we will need the whole package.json file. I believe one of your packages is somehow overriding our Nodeversion preference. Are you using any custom builder or zero config deployment?

Can you share a reproducible steps?

Unfortunately, this is not an open source project and I can't share the entire package.json files. However, before we go down the path of sharing a reproducible of an enterprise application, can you confirm that https://vercel.com/changelog/node-js-22-lts-is-now-available is not the cause of our failed builds?

Vercel

Node.js 22 LTS is now generally available for builds and functions - Vercel

Node.js version 22 is available as the runtime on Vercel for your builds and functions leveraging Node. Node 22 brings improved Stream performance, improved AbortSignal performance, improved Buffer performance, and improved CJS interoperability with ESM.

You announced Node.js 22 support on November 22. The first deployment we did after that announcement failed with an error telling us to upgrade to Node.js 22.

Once you confirm this is not the problem of our failed builds, I'll be able to justify the time investment to create a reproducible project.

I appreciate your help so far, as this is more than the radio silence I've gotten from the support ticket.

It appears that my colleague, Anna, has already identified the problem and responded via ticket. This was related to the outdated Sveltekit adapter that was unaware of the latest Node version. Please let us know if you have any questions.

For anyone else who ends up here in the future: If you have a monorepo with a package.json at the root-level and one at packages/xyz, the root-level file is used to determine the Node.js engine. A few other facts that apply to this:

• The Vercel project's root dir is set to packages/xyz
• The install command runs at the root