Replies: 1 comment
-
I'm fine with upgrading some dev deps to dependencies in order to make it work again, but there are other tools we are using such as vanilla-extract (CSS library that runs during build time) which in their official docs even say to install this next plugin as a dev dep: https://vanilla-extract.style/documentation/integrations/next/ So I guess overall just confused why this used to work and now does not. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
My team is working on upgrading one of our applications from Next v12 to v13. In doing so, the final hurdle is we are seeing this error upon starting the app in our Kubernetes/Container setup:
This package is used in next.config.js:
Now it sorta makes sense in my head that this should actually probably not be a dev dep, but it used to work in V12, so I'm trying to figure out what changed, as I didn't see anything about this in the migration docs: https://nextjs.org/docs/pages/building-your-application/upgrading/version-13
Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions