[Bug?]: CSS nesting selector gets encoded on server side
Duplicates
- [X] I have searched the existing issues
Latest version
- [X] I have tested the latest version
Current behavior 😯
When using the newly CSS nesting syntax (e.g. &:is(a)) the ampersand gets encoded as & on server side.
This leads to missing/wrong styles until the client side javascript is executed.
Expected behavior 🤔
The server shouldn't encode the ampersand in the CSS styles.
Steps to reproduce 🕹
Use this repo for simple reproduction: https://github.com/draconisNoctis/solidstart-css-nesting-issue
Context 🔦
No response
Your environment 🌎
No response
If I understand this right the CSS files themselves are being transformed nothing to do with JS. In which case is this a Vite or Nitro issue? Because Solid/SolidStart doesn't touch CSS. Very odd if Vite has an issue you'd think it would be more known.
I am running into the same issue I think. I am using css modules, and the SSR'ed response has all the ampersands encoded
I originally also thought this could be a vite and/or postcss issue, but I was pointed out on the solid discord server that this is an issue in solid-start. It appenrantly is handled correctly by solid-meta.