TypeError: Cannot read properties of undefined (reading 'clientModules')

Answered

Thrianta posted this in #help-forum

ThriantaOP

2024-02-12T08:54:44.000Z

Hey, i am getting this error when deploying to vercel, locally everything works just as expected, when deployed to vercel in prod, i get this error and the page returns this error

Answered by Thrianta

This error was after all due to vercel and not nextjs itself, vercel was not able to find client-manifest.json and other stuff for that specific route apparently something with build, after building locally and uploading the build it works perfectly

View full answer

37 Replies

Hong

2024-02-12T09:17:31.000Z

@Thrianta Have you tried to build your app locally? Can you provide the full error with the stack traces?

ThriantaOP

2024-02-12T09:18:08.000Z

lemme try building locally, because on dev server it works fine

â¨¯ TypeError: Cannot read properties of undefined (reading 'clientModules')
    at /var/task/node_modules/.pnpm/next@14.1.0_@opentelemetry+api@1.7.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:199008
    at rW (/var/task/node_modules/.pnpm/next@14.1.0_@opentelemetry+api@1.7.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:14861)
    at nM (/var/task/node_modules/.pnpm/next@14.1.0_@opentelemetry+api@1.7.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:47419)
    at nN (/var/task/node_modules/.pnpm/next@14.1.0_@opentelemetry+api@1.7.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:64674)
    at nG (/var/task/node_modules/.pnpm/next@14.1.0_@opentelemetry+api@1.7.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:72265)
    at AsyncLocalStorage.run (node:async_hooks:338:14)
    at Timeout._onTimeout (/var/task/node_modules/.pnpm/next@14.1.0_@opentelemetry+api@1.7.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:88128)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7) {
  page: '/profile/835137181504372806'
}

This is the stack trace in vercel dashboard

i can't build locally but not because of this but another bug with vercel CLI

Hong

2024-02-12T09:21:39.000Z

what? Can you run like npm run build?

ThriantaOP

2024-02-12T09:22:14.000Z

yup

no error when building locally

Hong

2024-02-12T09:25:28.000Z

Try to redeploy it, maybe.

ThriantaOP

2024-02-12T09:29:17.000Z

build task passes, every other page also works fine, just this single page shows up with an error

Hong

2024-02-12T09:29:58.000Z

Oh, can you provide the code for this page?

ThriantaOP

2024-02-12T09:30:36.000Z

yup, gimme a sec

Hong

2024-02-12T09:32:22.000Z

Why are you using 'use server' here?

I think removing it can fix the problem.

ThriantaOP

2024-02-12T09:34:45.000Z

that is there to just make sure the database function is not exported to the client

Hong

2024-02-12T09:37:00.000Z

To my knowledge, this code will only run on the server. I mean it's server-side rendering. It will not be exposed to the client side.

ThriantaOP

2024-02-12T09:43:39.000Z

but having 'use server' should not really change anything anyways

besides, if that was the case why would it work locally

joulev

2024-02-12T09:45:46.000Z

try upgrading nextjs version and redeploy without cache

i've seen scattered reports of this error which are fixed by updating versions and/or clearing .next

ThriantaOP

2024-02-12T09:46:56.000Z

i am on the latest version i think, 14.1.0

joulev

2024-02-12T09:48:03.000Z

seems related to this https://github.com/vercel/next.js/pull/60776

oh it's not in stable yet, only in canary

try canary then. v14.1.1-canary.10

ThriantaOP

2024-02-12T09:52:24.000Z

lemme try

ThriantaOP

2024-02-12T09:58:38.000Z

still same error after updating nextjs version, trying after removing build cache

joulev

2024-02-12T09:59:34.000Z

then im out of idea, sorry

it's working fine in my end

ThriantaOP

2024-02-12T10:00:04.000Z

exactly, locally it is working perfectly fine

not working even after removing build cache

Hong

2024-02-12T10:02:03.000Z

Do you set the env variables on vercel?

ThriantaOP

2024-02-12T10:12:32.000Z

yup

Hong

2024-02-12T10:14:38.000Z

Then, I have no idea. ðŸ«

ThriantaOP

2024-02-12T10:21:48.000Z

same

ThriantaOP

2024-02-12T10:50:43.000Z

for debug purposes i created a dummy api route where i was returning the user data to check if the database is causing this error, that route returned response just fine so that is not causing this error either

ThriantaOP

2024-02-13T13:09:22.000Z

Answer

Ant

2024-02-18T05:52:00.000Z

I resolved this issue by removing my Route Groups, that's folders that look like this '(folderName)' - these guys: https://nextjs.org/docs/app/building-your-application/routing/route-groups