You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generated source should be correctly generated without additional 0:, 1:.
Context
I did some digging around and the cssText which we get from here already contains invalid syntax. However the source code in each compilation gets transformed twice - I assume once for the server and once for the client. And one source code is vastly different from the other. I'm no expert in build tools but I'm guessing it's getting transformed by the swc and then the css is generated again from the transformed output. I'm not sure whether that is pigment or WyW-in-JS problem specifically.
I was also able to generate 1: when doing media queries. I might provide repro for that if necessary.
Steps to reproduce
Steps:
Basically it always generates incorrect syntax when using Next.js inside "use client" components when using
css` display: none;`
syntax.Current behavior
The app fails with
Expected behavior
Generated source should be correctly generated without additional
0:
,1:
.Context
I did some digging around and the
cssText
which we get from here already contains invalid syntax. However the source code in each compilation gets transformed twice - I assume once for the server and once for the client. And one source code is vastly different from the other. I'm no expert in build tools but I'm guessing it's getting transformed by the swc and then the css is generated again from the transformed output. I'm not sure whether that is pigment or WyW-in-JS problem specifically.I was also able to generate
1:
when doing media queries. I might provide repro for that if necessary.Your environment
npx @mui/envinfo
Search keywords: next nextjs client components server side rendering missed semicolon 0: swc interpolation
The text was updated successfully, but these errors were encountered: