Sizzling off the presses from Devon Govett, creator of Parcel, is Parcel CSS:
A CSS parser, transformer, and minifier written in Rust.
Good. The CSS world might use a bit processing shake up like this.
I simply wrote a number of weeks in the past:
Ya understand how esbuild has critically shaken issues up for the JavaScript processing world? Possibly we’d like a cssbuild? It might course of imports and do bundling (one thing we usually depend on Sass for). The purpose can be excessive velocity. Possibly it will be plugin-based and suitable with the PostCSS API in order that present PostCSS plugins would work on it. Possibly it might make sourcemaps and do modification. Possibly it will run your Sass, too, I dunno. However one thing to spark the CSS ecosystem like that may very well be cool.
It seems to be prefer it doesn’t do bundling (standalone anyway). I suppose it must simply invent a syntax for that, as I believe Sass considerably regrets the paradox of the way it makes use of @import similar to native CSS does and I wouldn’t blame anybody for not eager to go down that street. It’s difficult territory, for positive, as inventing syntax kinda places it into a unique class of instrument. I believe it will be price it although, as breaking apart CSS into smaller information however bundling them in growth is like… a factor folks do.
So why run your CSS by this factor? From the docs, it seems to be such as you’d wanna try this as a result of…
it’s a minifier (seems to be prefer it’s cssnano below the hood),it does vendor prefixing (seems to be prefer it’s Autoprefixer below the hood),it will probably course of as CSS modules (the traditional library, not the native ones), andyou get sourcemaps.
But it surely looks as if the killer Parcel CSS characteristic is what they’re calling “Syntax decreasing” that means you should use “future” CSS immediately (like, say, nesting) by having it processed right down to issues that browsers perceive, like Babel does in JavaScript.
Parcel CSS is quick and outputs small information. (Supply: @devongovett)
I don’t know what powers Parcel CSS. although it feels related in spirit to postcss-preset-env. I’m not sure if that’s what’s being leveraged or not. I suppose PostCSS is required for Autoprefixer which is getting used, so perhaps? I simply don’t see it within the package deal.json.
Will Parcel CSS turn into an ecosystem?
So I suppose the large query is: If Parcel CSS turns into the CSS parser of alternative, will we get plugins? And if we do, will it turn into a strong ecosystem like PostCSS plugins?
Parcel CSS: A New CSS Parser, Transformer, and Minifier initially printed on CSS-Methods. It’s best to get the e-newsletter and turn into a supporter.
Subscribe to MarketingSolution.
Receive web development discounts & web design tutorials.
Now! Lets GROW Together!