-
Notifications
You must be signed in to change notification settings - Fork 151
svelte-preprocess generate invalid CSS #191
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
Comments
Hey @wighawag 👋 Thanks for the report and the repro 😁 This is happening due to the change introduced in #168. The |
BREAKING CHANGE: 🧨 Uses Lookbehind assertions, so Node 9.11.2+ is needed ✅ Closes: Closes #191
This would be easily fixed with something like |
BREAKING CHANGE: 🧨 Uses Lookbehind assertions, so Node 9.11.2+ is needed ✅ Closes: Closes #191
BREAKING CHANGE: 🧨 Uses Lookbehind assertions, so Node 9.11.2+ is needed ✅ Closes: Closes #191
BREAKING CHANGE: 🧨 Uses Lookbehind assertions, so Node 9.11.2+ is needed ✅ Closes: Closes #191
BREAKING CHANGE: 🧨 Uses Lookbehind assertions, so Node 9.11.2+ is needed ✅ Closes: Closes #191
As I don't want to ruin the experience for those using node |
Just released |
BREAKING CHANGE: 🧨 Uses Lookbehind assertions, so Node 9.11.2+ is needed ✅ Closes: Closes #191
@vendaagil Can you share a repro? |
Describe the bug
svelte-preprocess generate invalid CSS when a global style include valid css using backslash
see sveltejs/svelte#5078
Logs
from https://github.com/wighawag/svelte-css-parser-error/
To Reproduce
Expected behavior
should build succesfully with valid css in
<style global > </style>
tagsStacktraces
see log above
Information about your Svelte project:
Your operating system: Windows 10
Svelte version : 3.23.2
Whether your project uses Webpack or Rollup : Rollup
Severity
It block me from using css library like
a17t
so pretty severe in my opinionThe text was updated successfully, but these errors were encountered: