Tailwind's --minify (Lightning CSS) randomly drops rules from the CDN .min.css files (parcel-bundler/lightningcss#1235). Minify with esbuild using Tailwind v4's browser targets instead, fail the build on esbuild warnings, and have npm run check fail if a .min.css file loses any selector from its unminified file.
* Stage npm releases from a release workflow, add CI checks, bump reallysimpledocs to 1.0.14
* Announce releases on Discord only after the site deploys
---------
Co-authored-by: grugbraindev <178141691+grugbraindev@users.noreply.github.com>
Emit dist/basecoat-{style}.bundle.css for every style pack, plus
dist/basecoat.bundle.css (Vega alias) and dist/basecoat-base.bundle.css.
Each is the uncompiled source with relative @imports inlined, so it can
be downloaded as one file (e.g. from jsDelivr) and imported after
tailwindcss. Compiling a bundle produces byte-identical output to the
split entrypoint.
Document the bundles on the installation page and fix the description
of basecoat-css/all.css, which is an alias for the default stylesheet.
Refs #150
Grug