From 10bd709e2e932129ecd27a11b3b9c0b0e6fbc68d Mon Sep 17 00:00:00 2001 From: Yann Date: Fri, 31 Jul 2026 17:11:49 -0700 Subject: [PATCH] Docs: tell PostCSS installers to copy .browserslistrc too The install section lists what to copy (framework/, your own folder, an entry file) but never mentioned .browserslistrc, so a source install inherited whatever browserslist target the host project already had. With a broader target postcss-preset-env starts polyfilling light-dark() and flattening nesting, which is exactly what 1.3.0 removed. The Browser support section already says to keep the file; this points at it from the place where the copying actually happens. Co-Authored-By: Claude Opus 5 --- src/content/docs/start.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/content/docs/start.mdx b/src/content/docs/start.mdx index 5453d2b..f8596c6 100644 --- a/src/content/docs/start.mdx +++ b/src/content/docs/start.mdx @@ -1,7 +1,7 @@ --- title: "Getting Started" description: "Copy mCSS into your project and learn the methodology: file structure, class syntax, components" -lastUpdate: 2026-07-28 +lastUpdate: 2026-07-31 version: 1 --- @@ -24,7 +24,7 @@ There is nothing to install from a registry: you copy mCSS into your project and ### Install with PostCSS -Copy [`src/styles/framework/`][framework-src] to wherever your CSS lives, then start your own folder next to it for your unlayered CSS. This site's [`site/`][site-src] is the worked example of that folder, and [`_global.css`][4] is the entry file tying the two together (see [the layers](#mcss-file-structure) below). +Copy [`src/styles/framework/`][framework-src] to wherever your CSS lives, then start your own folder next to it for your unlayered CSS. This site's [`site/`][site-src] is the worked example of that folder, and [`_global.css`][4] is the entry file tying the two together (see [the layers](#mcss-file-structure) below). Copy [`.browserslistrc`][browserslistrc] from the repo root as well: it sets the [compile floor](#browser-support) that keeps postcss-preset-env from polyfilling the features mCSS uses natively. You own the source this way: tokens, components, and themes are all editable, and you only ship the files you actually import. The cost is a build step, because the source uses `@custom-media`, which no browser understands yet. One plugin ([postcss-preset-env][presetEnv]) and a five-line config resolve it, and if you already use Astro, Vite, Next, or any other bundler, that config is the only thing you add. If you need more details on how to set up PostCSS, see [this blog post][postcss-post]. @@ -426,6 +426,7 @@ The exact compile floor lives in `.browserslistrc` (`baseline 2024`). Keep it: w [a11y]: /docs/global#accessibility [bem]: /blog/what-is-bem [bemit]: https://csswizardry.com/2015/08/bemit-taking-the-bem-naming-convention-a-step-further/ +[browserslistrc]: https://github.com/minimaldesign/mCSS/blob/main/.browserslistrc [components]: /components/start [coupling]: /blog/component-system-that-scales [discussions]: https://github.com/minimaldesign/mCSS/discussions