-
Notifications
You must be signed in to change notification settings - Fork 26.1k
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
13.2.2 changed build warnings to errors #46626
Comments
Hi, this should only be the case for the |
Yes
|
@ijjk Here is a real-world example: adeira/universe#5788 (check the failing CI) |
This ensures our config schema correctly validates with the default config we provide. Fixes: #46626 ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md)
Hi, this should now be updated in |
Works, thanks |
This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
Which area(s) of Next.js are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue
next build
To Reproduce
Have warnings as described in this issue #39161
Describe the Bug
13.2.1 had these issues as
warn
. Since 13.2.2 those are aserror
so the build fails.Expected Behavior
Warn but allow to build.
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
The text was updated successfully, but these errors were encountered: