rainbowindex 0.3.0 → 0.4.0

package/CHANGELOG.md

@@ -5,6 +5,49 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.4.0] - 2026-08-20
+
+### Added
+
+- **GitHub Packages publishing** — every release is now also published to
+  GitHub Packages as `@rainbowindex/rainbowindex` (that registry requires an
+  owner-scoped name). The README documents installing it under the usual
+  name via `pnpm add rainbowindex@npm:@rainbowindex/rainbowindex`, so all
+  documented imports and CLI invocations work unchanged.
+
+### Changed
+
+- **Stricter CLI argument validation** — the CLI is now driven by a
+  declarative command table that knows which flags and positionals each
+  command accepts. Flags used under the wrong command, stray positional
+  arguments, and flags missing their value are rejected with an error
+  instead of being silently ignored.
+- **Internal restructuring** (behavior-preserving, net ≈ −4,500 lines) —
+  the merge, scanner, and effects modules were split into focused modules;
+  the spacing/border prefix→property maps are now single-sourced from the
+  merge conflict table with a machine-checked parity test; `@apply` reuses
+  the engine's cascade ordering; the CLI and PostCSS builds share one
+  orchestration path with parallelized font fetches; and all internal
+  import cycles were broken. Public entry points are unchanged.
+
+### Fixed
+
+- **`ri()` stroke-width vs stroke-color conflict** — width-shaped `stroke-*`
+  classes (`stroke-2`, `stroke-1.5`, `stroke-[3px]`) were claiming the
+  `stroke` color property in the merge conflict table, so
+  `ri("stroke-2 stroke-red-500")` dropped `stroke-2` even though the two
+  classes set different CSS properties. The `stroke` prefix is now
+  width-vs-color dual-mode (mirroring `border`/`outline`): decimal and
+  non-color arbitrary values claim `stroke-width`, color values claim
+  `stroke`. Same-property conflicts (`stroke-2` vs `stroke-4`,
+  `stroke-red-500` vs `stroke-blue-500`) still merge as before.
+- **Watch mode double rebuild** — debouncing and rate-limiting now share a
+  single timer, so a burst of file changes landing inside the rate-limit
+  window schedules one rebuild instead of a redundant second one.
+- **`@color` entries without a colon** — a colon-less fragment in an
+  `@color` block now produces a warning and is skipped on its own; it no
+  longer swallowed the entry that followed it.
+
 ## [0.3.0] - 2026-08-14
 
 ### Added — editor tooling API (phase 2)

package/README.md

@@ -28,6 +28,28 @@ pnpm add rainbowindex
 
 Requires Node `>=20.19`. The package is **ESM-only** — there is no CommonJS build, so `require("rainbowindex")` is only supported on runtimes that can `require()` ES modules (Node 20.19+); use `import` otherwise (e.g. an ESM `postcss.config.js`/`.mjs`). `postcss` is a required peer dependency, `vite` an optional one; `lightningcss`, `chokidar`, and `tinyglobby` are bundled as direct deps.
 
+### From GitHub Packages
+
+Every release is also published to [GitHub Packages](https://github.com/rainbowindex/rainbowindex/pkgs/npm/rainbowindex) as `@rainbowindex/rainbowindex` — the same build under an owner-scoped name, which that registry requires. Point the scope at the registry in your project's `.npmrc`:
+
+```ini
+@rainbowindex:registry=https://npm.pkg.github.com
+```
+
+GitHub Packages authenticates every read, including public ones, so put a [personal access token (classic)](https://github.com/settings/tokens) with the `read:packages` scope in your `~/.npmrc`:
+
+```ini
+//npm.pkg.github.com/:_authToken=YOUR_TOKEN
+```
+
+Then install under the alias `rainbowindex`, so every import, `@import`, and CLI invocation in the docs below works unchanged:
+
+```sh
+pnpm add rainbowindex@npm:@rainbowindex/rainbowindex
+```
+
+Without the alias — `pnpm add @rainbowindex/rainbowindex` — the package resolves under its scoped name, and specifiers become `@rainbowindex/rainbowindex`, `@rainbowindex/rainbowindex/vite`, and so on.
+
 ## Quick start (Vite)
 
 The fastest path is the Vite plugin, which auto-injects PostCSS config and discovers your CSS entry on first dev-server listen.

package/dist/browser.d.ts

@@ -1,5 +1,5 @@
-export { C as ColorDefinition, a as CompilationContext, b as CompilationSnapshot, D as DEFAULT_TEXT_SIZES, F as FluidConfig, T as TextSize, c as Theme, d as createCompilationContext, e as createRi, f as defaultTheme, g as finalizeCompilationContext, r as registerColorNames, h as registerCustomFontFamilies, i as registerCustomTextSizes, j as registerCustomUtility, k as ri } from './index-CfDtWufj.js';
-export { s as safelist } from './safelist-CH3_PywB.js';
+export { C as ColorDefinition, a as CompilationContext, b as CompilationSnapshot, F as FluidConfig, T as TextSize, c as Theme, d as createCompilationContext, e as defaultTheme, f as finalizeCompilationContext, r as registerColorNames, g as registerCustomFontFamilies, h as registerCustomTextSizes, i as registerCustomUtility } from './context-ruu2x_jR.js';
+export { D as DEFAULT_TEXT_SIZES, c as createRi, r as ri, s as safelist } from './safelist-D9-Plqta.js';
 
 declare function browserEntryUnavailable(): never;
 

package/dist/browser.mjs

@@ -13,7 +13,7 @@ import {
   registerCustomTextSizes,
   registerCustomUtility,
   ri
-} from "./chunk-SOMDX7V6.mjs";
+} from "./chunk-5Y7EXXLS.mjs";
 
 // src/entries/browser.ts
 function browserEntryUnavailable() {

package/dist/chunk-3HRMFZGE.mjs

@@ -0,0 +1,19 @@
+// src/scanner/source-files.ts
+var SOURCE_FILE_EXTENSIONS = Object.freeze([
+  "html",
+  "js",
+  "jsx",
+  "ts",
+  "tsx",
+  "md",
+  "mdx",
+  "vue",
+  "svelte"
+]);
+function isSourceFile(file) {
+  return SOURCE_FILE_EXTENSIONS.some((ext) => file.endsWith(`.${ext}`));
+}
+
+export {
+  isSourceFile
+};