-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Unable to built Next.js since upgrading to v2 #11
Comments
Hello, Thank you for reporting! For v2, I’ve changed the bundling and distribution mechanism. Unfortunately, this may have resulted in broken builds in some environments. Currently, I’m on a vacation for 3 days, so I will take a look at |
@kripod sure, no rush. Thanks and enjoy the holidays! We've done a patch on our side for now 👍 |
Lovely, thank you! 🙌 May I ask how the patch works? That may take us closer to resolving the situation. |
This is the commit for it. It reverts to v1 😄 Plus it adds the types that Christian had added in this PR |
This should be resolved by v2.0.4. Thank you for reporting and please reach out if you encounter any further issues. Christian and you are doing awesome work with Stitches. I hope it will get big, especially with the recently added support for object syntax. |
Thanks @kripod will test it and get back to you! :) |
Hey @kripod
As you probably have seen I've been contributing to Stitches recently to help test it and make sure things are working as users would expect.
@christianalfoni has been working on improving the types and as part of the latest Stitches release, he upgraded to
react-polymorphic-box v2.0.3
Since this upgrade, I'm unable to get my Next.js project to build correctly. Things were working fine before that. We suspect it's something to do with the new build strategy used in v2.
I've abstracted a reproducible branch in this repo which you're free to clone and test it out.
Do you think this could be related to the latest release?
Let me know if there's any way I can help.
The text was updated successfully, but these errors were encountered: