-
Notifications
You must be signed in to change notification settings - Fork 2.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
Using next@13.0.1 causes build to fail due to nextCssLoader.issuer being undefined #12916
Comments
related #12912 |
Could you please link a repo we can use to reproduce the issue? It will help us identify the cause and fix it faster. |
@FrozenPandaz I'm having the same issue, here's a repo with it reproduced: https://github.com/smonn/repro-nx-and-nextjs As @violabg commented, I think #12912 is related. Update: still an issue in Next.js v13.0.2 and Nx v15.0.9 |
Next.js v13+ removed the 'issuer' field from their css/sass loaders. This breaks the nx-next plugin 'withNx'. This PR just adds a check to ensure the 'issuer' field is still there. Not the most robust fix but it should at least maintain backwards-compatibility w/ folks using next.js < 13. ISSUES CLOSED: nrwl#12916, nrwl#12912
Merged this PR #12973 which will fix this issue. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
Running
yarn build
will fail after upgrading fromnext@13.0.0
tonext@13.0.1
.Expected Behavior
The build process should run without issue: this is a regression because it used to work with next@13.0.0 installed.
Steps to Reproduce
Any routine installation will work, then upgrading the NextJs version to use
13.0.1
will cause the build to fail. The error comes from thewith-nx.ts
file reliance on theissuer
field (https://github.com/nrwl/nx/blob/master/packages/next/plugins/with-nx.ts#L83), which has been removed in next@13.0.1: https://github.com/vercel/next.js/pull/42106/filesFailure Logs
Environment
The text was updated successfully, but these errors were encountered: