Getting build error in vercel for getstaticProps pages since last build #49251

de-shine · 2023-05-04T21:44:53Z

de-shine
May 4, 2023

Summary

In Vercel the next js project build suddenly starts failing for all getStaticProps pages. any fix ?

Additional information

Check below error logs:
Error occurred prerendering page "/services/drywall-repair-1". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of null (reading 'useContext')
    at exports.useContext (/vercel/path0/node_modules/react/cjs/react.production.min.js:24:118)
    at $704cf1d3b684cc5c$export$9f8ac96af4b1b2ae (file:///vercel/path0/node_modules/@react-aria/ssr/dist/import.mjs:39:37)
    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 Ge (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:115:9)
    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)
    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)
    at Z (/vercel/path0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.browser.production.min.js:120:91)

Example

No response

laubonghaudoi · 2023-05-04T21:47:41Z

laubonghaudoi
May 4, 2023

+1 I am having the same error. Mine is TypeError: Cannot read properties of null (reading 'useEffect') instead of useContext. I suspect that this is caused by React hooks not accessible from server components. But I am using the /pages route not app/. Do we need to specify client components in /pages too? I tried adding 'use client' to the top of my component files and the error still persists. It could be a bug introduced in 13.4.

I assumed that upgrading to 13.4 is not breaking for projects that continue to use pages/. My local builds are successful and it only fails on Vercel.

Edit: opened a bug at #49261

1 reply

icyJoseph May 5, 2023

It should not matter. This must be a bug.

And yeah it looks like:

experimental: {
  appDir: false,
},

Does the trick, but it shouldn't be necessary.

joepetrillo · 2023-05-04T22:06:57Z

joepetrillo
May 4, 2023

I am having similar issues. My build works locally but Vercel does not like it. I am also only using the pages directory.

I am getting lots and lots of errors, but here are some which seem to follow a theme.

TypeError: Cannot read properties of null (reading 'useState')
Error occurred prerendering page "/404"
TypeError: Cannot read properties of null (reading 'useContext')

And so on...

0 replies

lucasishuman · 2023-05-05T00:16:57Z

lucasishuman
May 5, 2023

Same situation here. Even after rolling back to Next 13.3.4, which had been working to me before trying 13.4, and redeploying I'm still seeing issues on Vercel (but not locally) for pages using getServerSideProps. No other Next config changes. I'm also only using the pages directory.

E.g.

TypeError: Cannot read properties of null (reading 'useState')
    at exports.useState (/var/task/node_modules/react/cjs/react.production.min.js:25:394)
...

The site builds and deploys OK - but upon request, it bombs...

0 replies

laubonghaudoi · 2023-05-05T00:18:31Z

laubonghaudoi
May 5, 2023

Opened a bug here #49261

0 replies

skaraudio · 2023-05-05T01:25:25Z

skaraudio
May 5, 2023

I concur, we are also facing major issues. Tried reverting, doesn't worth either. Please help us to fix this as soon as possible. Our 50+ person company relies extensively on our backend with NextJs.

1 reply

kgilliam125 May 5, 2023

@skaraudio FYI that you can revert to Nextjs 13.3.4 to get back to a working state. I'm at least seeing success with my projects on this.

DrSh4dow · 2023-05-05T01:28:55Z

DrSh4dow
May 5, 2023

Same here; we are facing the same problem at my company.

Rolling back to Next 13.3.4 solves the problem tho

0 replies

skaraudio · 2023-05-05T01:50:59Z

skaraudio
May 5, 2023

Even with 13.3.4 I get this error..

1 reply

de-shine May 5, 2023
Author

+1. Its the same error for my company website as well.

w3bdesign · 2023-05-05T03:59:47Z

w3bdesign
May 5, 2023

2 replies

TravisHi May 5, 2023

@de-shine

Try adding the following to next.config.js:
experimental: {
  appDir: false,
},

Thank you! This was the solution for us (along with updating Next to 13.4.0 in our package.json).

de-shine May 5, 2023
Author

Thank you so much. The above config worked for me.

jd-carroll · 2023-05-05T04:36:15Z

jd-carroll
May 5, 2023

Also facing the same issue, here is a simple repro case:

Step 1:

test % npx create-next-app@latest --typescript
✔ What is your project named? … my-app
✔ Would you like to use ESLint with this project? … Yes
✔ Would you like to use Tailwind CSS with this project? … No
✔ Would you like to use `src/` directory with this project? … Yes
✔ Use App Router (recommended)? … No
✔ Would you like to customize the default import alias? … No
Creating a new Next.js app in /Users/my-profile/develop/test/my-app.

...

Step 2:

DO NOT cd INTO THE NEWLY CREATED APP!

test % npm install @vercel/analytics

Step 3:

test % cd my-app
my-app % npm run dev

> my-app@0.1.0 dev
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
event - compiled client and server successfully in 951 ms (169 modules)
wait  - compiling / (client and server)...
event - compiled client and server successfully in 626 ms (198 modules)
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
TypeError: Cannot read properties of null (reading 'useEffect')
    at useEffect (/Users/joseph/develop/andook/andook-client-workbench/node_modules/react/cjs/react.development.js:1634:21)
    at Analytics (file:///Users/joseph/develop/andook/andook-client-workbench/node_modules/@vercel/analytics/dist/react/index.js:132:3)
    at renderWithHooks (/Users/joseph/develop/andook/andook-client-workbench/test/my-app/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
    at renderIndeterminateComponent (/Users/joseph/develop/andook/andook-client-workbench/test/my-app/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5731:15)
    at renderElement (/Users/joseph/develop/andook/andook-client-workbench/test/my-app/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5946:7)
    at renderNodeDestructiveImpl (/Users/joseph/develop/andook/andook-client-workbench/test/my-app/node_modules/react-dom/cjs/react-dom-server.browser.development.js:6104:11)

2 replies

icyJoseph May 5, 2023

Why wouldn't you CD into the newly created project?

jd-carroll May 5, 2023

If you cd into the directory, it will work for some reason. Installing in the parent directory (similar to a monorepo setup) will force the error to occur.

icyJoseph · 2023-05-05T08:58:42Z

icyJoseph
May 5, 2023

Alright, this has been addressed here: #49274

For now explicitly setting appDir to false in the experimental block, works fine.

experimental: {
  appDir: false,
},

However, that setting will also be removed in an upcoming version: #49241 (comment)

0 replies

w3bdesign · 2023-05-05T21:25:53Z

w3bdesign
May 5, 2023

This issue has been resolved in 3.4.1 and you no longer need the appDir: false setting in next.config.

I removed it myself and my applications work.

@de-shine

0 replies

laubonghaudoi · 2023-05-12T06:12:14Z

laubonghaudoi
May 12, 2023

Just upgraded to 13.4.2 and this issue is occurring again. See #49261 (comment)

0 replies

Athrun-Judah · 2023-11-17T06:56:32Z

Athrun-Judah
Nov 17, 2023

the same error in 14.0.2

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Getting build error in vercel for getstaticProps pages since last build #49251

{{title}}

Replies: 13 comments 7 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Getting build error in vercel for getstaticProps pages since last build #49251

Summary

Additional information

Example

Replies: 13 comments · 7 replies

de-shine May 5, 2023 Author

de-shine May 5, 2023 Author

Step 1:

Step 2:

Step 3:

Replies: 13 comments 7 replies

de-shine May 5, 2023
Author

de-shine May 5, 2023
Author