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
Currently imports are not hoisted to the top of the CSS file. Instead, they are sorted down or remain nested (e.g. within media queries).
However, according to MDN, imported rules must precede all other types of rules, except @charset rules; as [@import] is not a nested statement it cannot be used inside conditional-group at-rules.
I propose that we follow the example of sass (see below) and hoist imports to the top. Perhaps in the future we could also accumulate queries in the process since they can be applied to @import statements directly.
Examples
purescript-css
in
query screen (singleton $ maxWidth nil) $
star & byClass "foo" ? do
importUrl "https://bomb.com/foo.css"
color black
Currently imports are not hoisted to the top of the CSS file. Instead, they are sorted down or remain nested (e.g. within media queries).
However, according to MDN, imported rules must precede all other types of rules, except
@charset
rules; as [@import
] is not a nested statement it cannot be used inside conditional-group at-rules.I propose that we follow the example of sass (see below) and hoist imports to the top. Perhaps in the future we could also accumulate queries in the process since they can be applied to
@import
statements directly.Examples
purescript-css
in
out
sass
in
out
The text was updated successfully, but these errors were encountered: