-
Notifications
You must be signed in to change notification settings - Fork 384
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
Invalid CSS breaks survey-core with NextJS 15 #6040
Comments
This was done to fix the surveyjs/survey-library#5507 issue |
@iotashan Probably you can setup to skip this rule check for this code, or for the whole |
Hello @iotashan, Thanks |
I also get the same error, tried the demo project and that works, set the package version to the same versions in my project, but then I get the same error. Will try to see if I can create something reproducible but the current project I cannot easily share. Any tips in the meantime how I could skip this check? |
Hello Everyone, In Next.js, you can configure PostCSS to ignore non-standard CSS rules. Add or modify your postcss.config.js as follows:
Alternatively, modify your Webpack configuration in next.config.js to suppress CSS warnings related to
I hope that either option can help you. |
Hi @JaneSjs, To reproduce the issue, you can modify the package.json file to enable Turbopack for next dev like this:
In Next.js 15, Turbopack is enabled by default for the development server when using create-next-app. I think it doesn't support certain CSS syntax, which is causing the error. https://nextjs.org/docs/app/api-reference/turbopack#unsupported-features When I remove this line in the css file I have recreated the issue, and you can check it in this codesandbox link https://codesandbox.io/p/devbox/v8r5hm |
survey-creator/packages/survey-creator-core/src/components/simulator.scss
Line 70 in f33bd23
::i-block-chrome
is not valid CSS, and breaks if you try to use survey-creator-react with Next.js 15import 'survey-creator-core/survey-creator-core.min.css';
The text was updated successfully, but these errors were encountered: