Build error on Vercel deployments after upgrading to 13.4

[laubonghaudoi]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
    Binaries:
      Node: 16.13.2
      npm: 9.6.4
      Yarn: 3.4.1
      pnpm: 7.21.0
    Relevant packages:
      next: 13.4.0
      eslint-config-next: 13.4.0
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue

none

To Reproduce

Upgrade next from ^13.3.4 tp ^13.4.0. The project is using pages/, not using app/dir nor turbopack.

Describe the Bug

I just updated the nextJS version from 13.3 to 13.4 without change anything in my codebase. The local build is successful without any errors, but when deployed on Vercel, I got hundreds of lines of error like

Error occurred prerendering page "/en/post/100". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of null (reading 'useEffect')
    at exports.useEffect (/vercel/path0/node_modules/react/cjs/react.production.min.js:24:292)
    at Analytics (file:///vercel/path0/node_modules/@vercel/analytics/dist/react/index.js:132:3)
    at Ge (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:114:273)
    at Z (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:120:91)
    at He (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:123:155)
    at Je (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:122:100)
    at Z (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:120:222)
    at Ge (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:119:95)
    at Z (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:120:91)
    at Ge (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:115:9)

I speculate that this is caused by my components not being specified as client components. But I am not using the app/ directory, I am only using the /pages. Does that mean I need to specify client components even if I am using /pages? I tried adding 'use client' to the top of my component files and the error still persists.

The local builds are successful without any errors, this only happens on Vercel deployments.

Expected Behavior

Build should be successful with no error.

Which browser are you using? (if relevant)

irrelevant

How are you deploying your application? (if relevant)

Vercel

[lucasishuman]

FYI - related discussion - #49251

[kgilliam125]

@laubonghaudoi Ran into the same issue you're describing with a previously working build. This is silly, but did you make sure to yarn/npm install again after you reverted the version in your package.json?

My build seems to be running again on Next 13.3.4 but is broken in 13.4

[benjwexler]

I was facing a similar issue after trying to upgrade locally for a Next app using a custom server. Adding the following to next.config.js seems to have fixed the issue:

experimental: {
  appDir: false,
},

[joachimjusth]

I had also the same issue when I did the migration to Next 13.4.

I added the flag given by @benjwexler , and now it deploy without any issue.

I was facing a similar issue after trying to upgrade locally for a Next app using a custom server. Adding the following to next.config.js seems to have fixed the issue:

experimental: {
  appDir: false,
},

[skaraudio]

I was facing a similar issue after trying to upgrade locally for a Next app using a custom server. Adding the following to next.config.js seems to have fixed the issue:

experimental: {
  appDir: false,
},

Thank you!!

[lucasishuman]

Thanks for the config tips, all.

Next needs to add that to the pages docs if it's now explicitly required to 'opt out' of app directory...

https://nextjs.org/docs/pages/api-reference/next-config-js

[belgattitude]

Have the same issue after upgrade to nextjs 13.4.0 (from 13.3.4) - no app dir - no type module

The example repo is:

https://github.com/belgattitude/nextjs-monorepo-example (branch main)

The ci passes (https://github.com/belgattitude/nextjs-monorepo-example/actions/workflows/ci-nextjs-app.yml), vercel just started to break after upgrade.

If you want to try on vercel, you'll have to add ENABLE_EXPERIMENTAL_COREPACK=1 in the vercel env.

The deployment url: https://monorepo-nextjs-app.vercel.app/

Open to help if needed

PS:

• might be related to [NEXT-1032] A Node.js API is used (process.turbopack at line: 47) which is not supported in the Edge Runtime. #48302 as well
• seems it will be fixed in Fix require-hook with just pages on deploy #49274