-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Vercel deployment results in TypeError: Cannot read properties of null (reading 'useMemo') #1399
Comments
Having same issue :-( The local build works fine.
|
I can reproduce the issue with your repo, but it does not happen on one I created myself with the same version/packages: https://github.com/c-ehrlich/test2 https://test2-vert-one.vercel.app/ Can you confirm that you're able to deploy my repo? |
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://test2-vert-one.vercel.app/ |
Strange I was able to deploy it with your repo. Can you try to reproduce with my repo using |
@pavan38kp @c-ehrlich maybe it works because it is fixed with |
So upgrading to 13.4 would help? |
If by "help" you mean reproduce the reported issue - then yes ;-) |
Alrught, I'm trying this now. |
Well, I tried to reproduce with next |
Same issues, same solution |
I tried to upgrade to latest version of all libraries, but it didn't help either. Upgrade:
I am using base version from T3 generator using all libraries except Tailwindcss (compared to https://github.com/pavankpdev/sica I am using next-auth). But same error for me. I am using npm and MacOS. Node version v18.16.0 |
See also trpc/trpc#4316 |
Just a heads up, I just tried to deploy the app on Netlify and it worked. |
Same issue here with a fresh template https://github.com/esthevann/chirp |
Same problen |
As said by @c-ehrlich just change in your dependencies in package.json |
Can confirm that this worked for me! |
@baseba thank you a lot. You guys are awesome. Now it works. Thanx. |
yes Thanks @baseba it works now |
Can confirm that it's caused by this trpc/trpc#4316 Let's pin Next to 13.2.4 until that is fixed. I'm writing the pr now and will subscribe to the issue so that we can undo the pinning asap. Thanks @pavan38kp @michalbundyra for finding and profiling this. Will leave this open for the time being so that people who have scaffolded with the bug can see it :) |
@c-ehrlich 13.3.4 is also fine, the problem is only with 13.4.0, any previous version works fine. |
Seems to be fixed now with NextJS 13.4.1 - probably in vercel/next.js#49274 |
I can confirm 13.4.1 works - tested in belgattitude/nextjs-monorepo-example#3775 |
Provide environment information
System:
OS: macOS 11.6.1
CPU: (8) arm64 Apple M1
Memory: 112.23 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 18.13.0 - /usr/local/bin/node
Yarn: 1.22.17 - ~/.yarn/bin/yarn
npm: 8.19.3 - /usr/local/bin/npm
Describe the bug
This issue occurs when an attempt is made to deploy the application on Vercel.
Reproduction repo
https://github.com/pavankpdev/sica
To reproduce
Additional information
The text was updated successfully, but these errors were encountered: