-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Fixes issue with next/dynamic when running next version > 12.0.3 #618
Conversation
Someone is attempting to deploy a commit to the Vercel Solutions Team on Vercel. A member of the Team first needs to authorize it. |
This pull request is being automatically deployed with Vercel (learn more). commerce-local – ./🔍 Inspect: https://vercel.com/vercel-solutions-vtest314/commerce-local/5EQ8JMcwLTwcq8LtkCGras8Wt5c2 |
Updated to use prop spreading as suggested by @ancaemcken |
@@ -31,22 +31,31 @@ const dynamicProps = { | |||
|
|||
const SignUpView = dynamic( | |||
() => import('@components/auth/SignUpView'), | |||
dynamicProps | |||
{ | |||
...dynamicProps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the cases that we don't need to extend the object can you leave it like before? Or does it have any problem with it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dynamic()
needs an object literal, the way it was before was causing the issue
…cel#618) Co-authored-by: mdupree <[email protected]>
Fixes issue seen with next/dynamic when running yarn install due to problems with newer versions of next
Regarding issue #614
vercel/next.js#31683