-
Notifications
You must be signed in to change notification settings - Fork 26.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
Build Error: Parsing css source code failed #66394
Comments
Was able to verify that the root cause is this package CSS file you're using: https://unpkg.com/@formio/js@5.0.0-rc.48/dist/formio.full.min.css When that is put into the Lightning CSS playground it highlights an error on this declaration: .formio-dialog.formio-dialog-theme-default .formio-dialog-buttons {
*zoom: 1;
} Specifically Specific code is here: https://github.com/formio/formio.js/blame/e1f926e090cf6d36e7cd05e58fb231a939b3ab30/src/sass/formio.form.scss#L703-L705 |
@timneutkens how it is being parsed in normal mode? Only happened in turbo mode ![]() |
With webpack we use postcss currently, which is much slower. |
Currently this file includes invalid CSS which fails to parse on some of the modern tooling like lightningcss.dev. Since IE7 is severely outdated I don't think this property is needed nowadays, given that even IE11 is fully deprecated. Details on the Next.js repo: vercel/next.js#66394
I've opened a PR to remove the invalid CSS from the library that you're using: formio/formio.js#5635. |
Currently this file includes invalid CSS which fails to parse on some of the modern tooling like lightningcss.dev. Since IE7 is severely outdated I don't think this property is needed nowadays, given that even IE11 is fully deprecated. Details on the Next.js repo: vercel/next.js#66394
They landed the change! I'm going to close this issue as it's not a bug in Turbopack 🙏 Thanks for the report though! |
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Link to the code that reproduces this issue
https://github.com/balaji-sivasakthi/turbo-css-parser-issue
To Reproduce
npm install
.npm run dev
.Running without Turbo works fine, but with Turbo, the session is not working properly. It seems there is a problem with the CSS parser.
Current vs. Expected behavior
Current
When running the application with Turbo, the session is not functioning correctly due to issues with the CSS parser.
Expected behavior
The application should function correctly with Turbo, without any issues related to the CSS parser.
Provide environment information
Operating System: Platform: darwin Arch: arm64 Version: Darwin Kernel Version 23.5.0: Wed May 1 20:19:05 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T8112 Available memory (MB): 8192 Available CPU cores: 8 Binaries: Node: 18.19.1 npm: 10.8.0 Yarn: 1.22.21 pnpm: 8.15.8 Relevant Packages: next: 14.2.3 // Latest available version is detected (14.2.3). eslint-config-next: 14.2.3 react: 18.3.1 react-dom: 18.3.1 typescript: 5.4.5 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Font (next/font), Turbopack
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
Build Error
Failed to compile
Next.js (14.2.3) (turbo)
./node_modules/@formio/js/dist/formio.full.min.css:5:97528
Parsing css source code failed
3 | * Copyright 2019-2024 The Bootstrap Authors
4 | * Licensed under MIT (https://github.com/twbs/icons/blob/main/LICENSE)
The text was updated successfully, but these errors were encountered: