I'm reacting to the PR #47 (Add a note about dropping Sass in favor of native CSS) as i 100% share this vision....
But :)
I'll have a need for a year or two i guess for the only remaining sass feature i still use : import / include.
I know HTTP2 may seem to be the answer-to-everything, but with layers and scope coming, there is still imho a need for packed / ordered CSS files (and for serial CSS-splitter like me that can avoid a LOT of useless HTTP requests, even if shared in one connection).
I'd like a simple feature to "compile" (big word there) multiple CSS into one...
My guess would be that this need is a common one in the "from SASS to CSS" transition, but I'd totally understand if you think this should be in a symfonycast/css-bundle, or a simon/css-yourself one 😄
Or maybe @weaverryan this should only be a dedicated "compiler" inside AssetMapper ?
I'm reacting to the PR #47 (Add a note about dropping Sass in favor of native CSS) as i 100% share this vision....
But :)
I'll have a need for a year or two i guess for the only remaining sass feature i still use : import / include.
I know HTTP2 may seem to be the answer-to-everything, but with layers and scope coming, there is still imho a need for packed / ordered CSS files (and for serial CSS-splitter like me that can avoid a LOT of useless HTTP requests, even if shared in one connection).
I'd like a simple feature to "compile" (big word there) multiple CSS into one...
My guess would be that this need is a common one in the "from SASS to CSS" transition, but I'd totally understand if you think this should be in a symfonycast/css-bundle, or a simon/css-yourself one 😄
Or maybe @weaverryan this should only be a dedicated "compiler" inside AssetMapper ?
WDYT ?