Closed Yard-Daniel closed 1 year ago
I think this should have been fixed in the latest codebase, as we check !updatedModules
here so it can't be null
or undefined
in the place you pointed out:
Let us know if you still see it in the latest canary, thanks.
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
Verify canary release
Provide environment information
Which area(s) of Next.js are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue
https://stackblitz.com/edit/vercel-next-js-chqhja?file=app%2Fpage.tsx
To Reproduce
Setup turbo monorepo with a nextjs13 project.
pnpm dev
The error mostly occurs and seldom disappears, because of the hot.module (not sure what triggers).
It fails in the nextjs13 webpack bundle.
Describe the Bug
file: packages/next/src/client/components/react-dev-overlay/hot-reloader-client.tsx line: 153
// current const hasUpdates = Boolean(updatedModules.leng
th)
// should be const hasUpdates = Boolean(updatedModules && updatedModules.length)
// because error Boolean(null.length) // TypeError: Cannot read properties of null (reading 'length') obviously.
Expected Behavior
To run
pnpm dev
without issues from the nextjs13 build.Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response