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
Which first gets the bundle from components, and only then add to it other CSS files. This is a little problematic due to the CSS cascade, like in this case, when using @import. From MDN:
An @import rule must be defined at the top of the stylesheet, before any other at-rule (except @charset and @layer) and style declarations, or it will be ignored.
If I won't use the @import and write styles directly in index.css processing is successful, but produced CSS is still out of order.
Here's a repo to reproduce the issue. Clone it, copy env.expamle to .env, and run either npm start or npm run build to observe the issue.
NOTE: If not using @import the component-first processing can be worked around but defining explicit CSS ordering with @layer. Using @import currently prevents any successful build.
The text was updated successfully, but these errors were encountered:
I'm trying to use Lightning CSS to transform CSS files but it fails with:
To make 11ty aware of my CSS I've these in the main
webc
layout file:Which first gets the bundle from components, and only then add to it other CSS files. This is a little problematic due to the CSS cascade, like in this case, when using
@import
. From MDN:If I won't use the
@import
and write styles directly inindex.css
processing is successful, but produced CSS is still out of order.Related issue @11ty/webc.
Here's a repo to reproduce the issue. Clone it, copy
env.expamle
to.env
, and run eithernpm start
ornpm run build
to observe the issue.NOTE: If not using
@import
the component-first processing can be worked around but defining explicit CSS ordering with@layer
. Using@import
currently prevents any successful build.The text was updated successfully, but these errors were encountered: