mCSS 1.2.0 #55
minimaldesign
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
mCSS 1.2.0 splits the drop-in framework file in two.
mcss.cssis now the framework core on its own (~17 KB min+gzip), and the component library moves into its own file,mcss.components.css(~5 KB min+gzip). If you build your own components on top of mCSS, you stop shipping a library you never use. If you want the library, you add one more line.mCSS follows the copy-it-you-own-it model: there is no package to update. Grab
dist/mcss.css(ormcss.min.css), copy the pieces you want, and edit them like anything else you wrote.What's new
mcss.components.css: the component library has its own entry file. All 25component.*.cssfiles import there wrapped in@layer components, anddist/gains the matching drop-insmcss.components.cssandmcss.components.min.css.mcss.cssdeclares the layer order, so the library lands in itscomponentsslot wherever you put the link, exactly like the existingthemeslot:Breaking changes
dist/mcss.cssanddist/mcss.min.cssare the framework core only. Settings, base, elements, global, and helpers, plus the emptycomponentsandthemelayer slots. If you use the component library, adddist/mcss.components.min.cssnext to it, or your components will lose their styles.framework/mcss.cssno longer importscomponent.*.css. Add@import url(./framework/mcss.components.css);to your entry file next to the existing framework import (see_global.css).Nothing changed inside the components themselves. Every class, token, and Astro component works exactly as it did in 1.1.0; this release is only about which file they arrive in.
The full list is in the changelog. Built something with mCSS? Come show it off in the discussions.
This discussion was created from the release mCSS 1.2.0.
All reactions