@tenphi/tasty 0.0.0-snapshot.d2dcdeb → 0.0.0-snapshot.d4ccea8

package/dist/zero/index.d.ts

@@ -1,3 +1,81 @@
-import { ExtractedChunk, ExtractedSelector, extractStylesForSelector, extractStylesWithChunks } from "./extractor.js";
-import { CSSWriter } from "./css-writer.js";
-export { CSSWriter, type ExtractedChunk, type ExtractedSelector, extractStylesForSelector, extractStylesWithChunks };
+import { b as Styles } from "../index-BcsaHo8x.js";
+
+//#region src/zero/extractor.d.ts
+interface ExtractedChunk {
+  className: string;
+  css: string;
+}
+interface ExtractedSelector {
+  selector: string;
+  css: string;
+}
+/**
+ * Extract styles using chunking (for className mode).
+ * Returns multiple classes, one per chunk.
+ */
+declare function extractStylesWithChunks(styles: Styles): ExtractedChunk[];
+/**
+ * Extract styles for a specific selector (for global/selector mode).
+ * Returns a single CSS block.
+ */
+declare function extractStylesForSelector(selector: string, styles: Styles): ExtractedSelector;
+//#endregion
+//#region src/zero/css-writer.d.ts
+interface CSSWriterOptions {
+  /** Enable source comments in output (e.g., "from: Button.tsx") */
+  devMode?: boolean;
+}
+declare class CSSWriter {
+  private cssBlocks;
+  private outputPath;
+  private devMode;
+  constructor(outputPath: string, options?: CSSWriterOptions);
+  /**
+   * Add CSS block with deduplication key
+   * @param key - Unique key for deduplication
+   * @param css - CSS content
+   * @param source - Optional source file path (used in devMode)
+   */
+  add(key: string, css: string, source?: string): void;
+  /**
+   * Check if a key already exists
+   */
+  has(key: string): boolean;
+  /**
+   * Get the number of CSS blocks
+   */
+  get size(): number;
+  /**
+   * Write all collected CSS to the output file
+   */
+  write(): void;
+  /**
+   * Get all CSS as string (for testing or in-memory use)
+   */
+  getCSS(): string;
+  /**
+   * Clear all collected CSS
+   */
+  clear(): void;
+  /**
+   * Get the output path
+   */
+  getOutputPath(): string;
+}
+/**
+ * Factory for creating a {@link CSSWriter} instance.
+ *
+ * Canonical functional entry point; the `CSSWriter` class remains exported
+ * for advanced/internal use.
+ *
+ * @example
+ * ```ts
+ * import { createCSSWriter } from '@tenphi/tasty/zero';
+ *
+ * const writer = createCSSWriter('output.css', { devMode: true });
+ * ```
+ */
+declare function createCSSWriter(outputPath: string, options?: CSSWriterOptions): CSSWriter;
+//#endregion
+export { CSSWriter, type CSSWriterOptions, type ExtractedChunk, type ExtractedSelector, createCSSWriter, extractStylesForSelector, extractStylesWithChunks };
+//# sourceMappingURL=index.d.ts.map

package/dist/zero/index.js

@@ -1,3 +1,2 @@
-import { extractStylesForSelector, extractStylesWithChunks } from "./extractor.js";
-import { CSSWriter } from "./css-writer.js";
-export { CSSWriter, extractStylesForSelector, extractStylesWithChunks };
+import { c as extractStylesForSelector, l as extractStylesWithChunks, n as createCSSWriter, t as CSSWriter } from "../css-writer-C8ShXK5R.js";
+export { CSSWriter, createCSSWriter, extractStylesForSelector, extractStylesWithChunks };

package/dist/zero/next.d.ts

@@ -1,4 +1,4 @@
-import { TastyZeroConfig } from "./babel.js";
+import { r as TastyZeroConfig } from "../babel-eMs_zZjM.js";
 
 //#region src/zero/next.d.ts
 interface WebpackConfigContext {

package/dist/zero/next.js

@@ -20,7 +20,7 @@ import { fileURLToPath } from "url";
 * @example
 * ```javascript
 * // next.config.js
-* const { withTastyZero } = require('@tenphi/tasty/next');
+* const { withTastyZero } = require('@tenphi/tasty/zero/next');
 *
 * module.exports = withTastyZero({
 *   output: 'public/tasty.css',

package/dist/zero/next.js.map

@@ -1 +1 @@
-{"version":3,"file":"next.js","names":[],"sources":["../../src/zero/next.ts"],"sourcesContent":["/**\n * Next.js configuration wrapper for tasty-zero.\n *\n * Supports both webpack and Turbopack bundlers:\n * - **webpack**: Injects a babel-loader rule with the tasty-zero Babel plugin\n *   via `webpack()` config hook. Config is passed as a jiti factory function.\n * - **Turbopack**: Adds a `turbopack.rules` entry with babel-loader and\n *   JSON-serializable options (`configFile` path instead of a function).\n *   The Babel plugin loads the config internally via jiti.\n *\n * The generated CSS is injected automatically — `@tenphi/tasty/static`\n * imports are replaced with an import of the output CSS file at build time.\n * No manual CSS import in layout files is needed.\n *\n * @example\n * ```javascript\n * // next.config.js\n * const { withTastyZero } = require('@tenphi/tasty/next');\n *\n * module.exports = withTastyZero({\n *   output: 'public/tasty.css',\n *   configFile: './app/tasty-zero.config.ts',\n * })({\n *   // your Next.js config\n * });\n * ```\n */\n\nimport { createRequire } from 'module';\nimport * as path from 'path';\nimport { fileURLToPath } from 'url';\n\nimport { createJiti } from 'jiti';\n\nimport type { TastyZeroBabelOptions, TastyZeroConfig } from './babel';\n\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = path.dirname(__filename);\n\n// Next.js types (inline to avoid requiring next as a dependency)\ninterface WebpackConfigContext {\n  isServer: boolean;\n  dev: boolean;\n  buildId: string;\n  dir: string;\n}\n\n/* eslint-disable @typescript-eslint/no-explicit-any -- webpack/Next.js config types are complex */\ninterface TurbopackLoaderItem {\n  loader: string;\n  options?: Record<string, unknown>;\n}\n\ninterface TurbopackRuleConfig {\n  loaders: (string | TurbopackLoaderItem)[];\n  as?: string;\n  condition?: unknown;\n}\n\ninterface TurbopackConfig {\n  rules?: Record<string, TurbopackRuleConfig | TurbopackRuleConfig[]>;\n  [key: string]: unknown;\n}\n\ninterface NextConfig {\n  webpack?: (config: any, context: WebpackConfigContext) => any;\n  turbopack?: TurbopackConfig;\n  [key: string]: unknown;\n}\n\nexport interface TastyZeroNextOptions {\n  /**\n   * Output path for CSS relative to project root.\n   * @default 'public/tasty.css'\n   */\n  output?: string;\n\n  /**\n   * Whether to enable the plugin.\n   * @default true\n   */\n  enabled?: boolean;\n\n  /**\n   * Tasty configuration for build-time processing.\n   * For static configs that don't change during dev.\n   *\n   * For configs that depend on theme files, use `configFile` instead.\n   */\n  config?: TastyZeroConfig;\n\n  /**\n   * Path to a TypeScript/JavaScript module that exports the tasty zero config\n   * as its default export. The module is re-evaluated on each\n   * compilation, enabling hot reload when the file (or its imports) change.\n   *\n   * @example './app/tasty-zero.config.ts'\n   */\n  configFile?: string;\n\n  /**\n   * Extra file paths (relative to project root) that the config depends on.\n   * When any of these files change, the Babel cache is invalidated and\n   * the config is re-evaluated.\n   *\n   * The `configFile` itself is always tracked automatically.\n   * Use this for transitive dependencies that aren't directly imported\n   * by the config file, or when using `config` instead of `configFile`.\n   *\n   * @example ['./app/theme.ts']\n   */\n  configDeps?: string[];\n\n  /**\n   * Output mode for extracted CSS.\n   *\n   * - `'file'` (default): CSS is written to a single output file.\n   * - `'inject'`: CSS is embedded inline in JS and injected at runtime.\n   *   No CSS file is written. Best for reusable components and extensions.\n   *\n   * When `mode` is `'inject'`, `output` is ignored.\n   *\n   * @default 'file'\n   */\n  mode?: 'file' | 'inject';\n}\n\n/**\n * Next.js configuration wrapper for tasty-zero.\n * Configures both webpack and Turbopack bundlers automatically.\n */\nexport function withTastyZero(options: TastyZeroNextOptions = {}) {\n  const {\n    output = 'public/tasty.css',\n    enabled = true,\n    config: tastyConfig,\n    configFile,\n    configDeps = [],\n    mode,\n  } = options;\n\n  return (nextConfig: NextConfig = {}): NextConfig => {\n    if (!enabled) {\n      return nextConfig;\n    }\n\n    const projectDir = process.cwd();\n    const absoluteOutput = path.resolve(projectDir, output);\n    const babelPluginPath = path.resolve(__dirname, 'babel.js');\n\n    const absoluteConfigFile = configFile\n      ? path.resolve(projectDir, configFile)\n      : undefined;\n\n    const allDeps = [\n      ...(absoluteConfigFile ? [absoluteConfigFile] : []),\n      ...configDeps.map((dep) => path.resolve(projectDir, dep)),\n    ];\n\n    // --- Turbopack configuration ---\n    // Turbopack loader options must be JSON-serializable (no functions).\n    // The Babel plugin loads config internally via `configFile` path + jiti.\n    const turbopackBabelOptions: Record<string, unknown> = {\n      babelrc: false,\n      configFile: false,\n      parserOpts: {\n        plugins: ['typescript', 'jsx', 'decorators-legacy'],\n      },\n      plugins: [\n        [\n          babelPluginPath,\n          {\n            output: absoluteOutput,\n            injectImport: true,\n            ...(mode ? { mode } : {}),\n            ...(absoluteConfigFile\n              ? { configFile: absoluteConfigFile }\n              : tastyConfig\n                ? { config: tastyConfig }\n                : {}),\n            ...(allDeps.length > 0 ? { configDeps: allDeps } : {}),\n          },\n        ],\n      ],\n    };\n\n    const existingTurbopack = nextConfig.turbopack || {};\n    const existingRules = existingTurbopack.rules || {};\n\n    const existingExperimental =\n      (nextConfig.experimental as Record<string, unknown>) || {};\n\n    return {\n      ...nextConfig,\n\n      experimental: {\n        ...existingExperimental,\n        turbopackUseBuiltinBabel: true,\n      },\n\n      turbopack: {\n        ...existingTurbopack,\n        rules: {\n          ...existingRules,\n          '*.{ts,tsx,js,jsx}': {\n            condition: { not: 'foreign' },\n            loaders: [\n              {\n                loader: 'babel-loader',\n                options: turbopackBabelOptions,\n              },\n            ],\n          },\n        },\n      },\n\n      webpack(config: any, context: WebpackConfigContext) {\n        const { dir } = context;\n\n        const wpProjectDir = dir || projectDir;\n        const wpAbsoluteOutput = path.resolve(wpProjectDir, output);\n        const projectRequire = createRequire(\n          path.resolve(wpProjectDir, 'package.json'),\n        );\n\n        const wpAbsoluteConfigFile = configFile\n          ? path.resolve(wpProjectDir, configFile)\n          : undefined;\n\n        const wpAllDeps = [\n          ...(wpAbsoluteConfigFile ? [wpAbsoluteConfigFile] : []),\n          ...configDeps.map((dep) => path.resolve(wpProjectDir, dep)),\n        ];\n\n        const babelPluginOptions: TastyZeroBabelOptions = {\n          output: wpAbsoluteOutput,\n          injectImport: true,\n          ...(mode ? { mode } : {}),\n        };\n\n        if (wpAbsoluteConfigFile) {\n          const jiti = createJiti(wpProjectDir, {\n            moduleCache: false,\n          });\n\n          babelPluginOptions.config = () => {\n            return jiti(wpAbsoluteConfigFile) as TastyZeroConfig;\n          };\n        } else if (tastyConfig) {\n          babelPluginOptions.config = tastyConfig;\n        }\n\n        if (wpAllDeps.length > 0) {\n          babelPluginOptions.configDeps = wpAllDeps;\n        }\n\n        const babelPluginConfig = [babelPluginPath, babelPluginOptions];\n\n        const existingRule = config.module?.rules?.find(\n          (rule: any) =>\n            rule.use?.loader === 'babel-loader' ||\n            rule.use?.some?.((u: any) => u.loader === 'babel-loader'),\n        );\n\n        if (existingRule) {\n          const babelUse = Array.isArray(existingRule.use)\n            ? existingRule.use.find((u: any) => u.loader === 'babel-loader')\n            : existingRule.use;\n\n          if (babelUse?.options) {\n            babelUse.options.plugins = babelUse.options.plugins || [];\n            babelUse.options.plugins.push(babelPluginConfig);\n          }\n        } else {\n          config.module = config.module || {};\n          config.module.rules = config.module.rules || [];\n          config.module.rules.push({\n            test: /\\.(tsx?|jsx?)$/,\n            exclude: /node_modules/,\n            use: [\n              {\n                loader: projectRequire.resolve('babel-loader'),\n                options: {\n                  babelrc: false,\n                  configFile: false,\n                  parserOpts: {\n                    plugins: ['typescript', 'jsx', 'decorators-legacy'],\n                  },\n                  plugins: [babelPluginConfig],\n                },\n              },\n            ],\n          });\n        }\n\n        if (typeof nextConfig.webpack === 'function') {\n          return nextConfig.webpack(config, context);\n        }\n\n        return config;\n      },\n    };\n  };\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAoCA,MAAM,aAAa,cAAc,OAAO,KAAK,IAAI;AACjD,MAAM,YAAY,KAAK,QAAQ,WAAW;;;;;AA8F1C,SAAgB,cAAc,UAAgC,EAAE,EAAE;CAChE,MAAM,EACJ,SAAS,oBACT,UAAU,MACV,QAAQ,aACR,YACA,aAAa,EAAE,EACf,SACE;AAEJ,SAAQ,aAAyB,EAAE,KAAiB;AAClD,MAAI,CAAC,QACH,QAAO;EAGT,MAAM,aAAa,QAAQ,KAAK;EAChC,MAAM,iBAAiB,KAAK,QAAQ,YAAY,OAAO;EACvD,MAAM,kBAAkB,KAAK,QAAQ,WAAW,WAAW;EAE3D,MAAM,qBAAqB,aACvB,KAAK,QAAQ,YAAY,WAAW,GACpC,KAAA;EAEJ,MAAM,UAAU,CACd,GAAI,qBAAqB,CAAC,mBAAmB,GAAG,EAAE,EAClD,GAAG,WAAW,KAAK,QAAQ,KAAK,QAAQ,YAAY,IAAI,CAAC,CAC1D;EAKD,MAAM,wBAAiD;GACrD,SAAS;GACT,YAAY;GACZ,YAAY,EACV,SAAS;IAAC;IAAc;IAAO;IAAoB,EACpD;GACD,SAAS,CACP,CACE,iBACA;IACE,QAAQ;IACR,cAAc;IACd,GAAI,OAAO,EAAE,MAAM,GAAG,EAAE;IACxB,GAAI,qBACA,EAAE,YAAY,oBAAoB,GAClC,cACE,EAAE,QAAQ,aAAa,GACvB,EAAE;IACR,GAAI,QAAQ,SAAS,IAAI,EAAE,YAAY,SAAS,GAAG,EAAE;IACtD,CACF,CACF;GACF;EAED,MAAM,oBAAoB,WAAW,aAAa,EAAE;EACpD,MAAM,gBAAgB,kBAAkB,SAAS,EAAE;EAEnD,MAAM,uBACH,WAAW,gBAA4C,EAAE;AAE5D,SAAO;GACL,GAAG;GAEH,cAAc;IACZ,GAAG;IACH,0BAA0B;IAC3B;GAED,WAAW;IACT,GAAG;IACH,OAAO;KACL,GAAG;KACH,qBAAqB;MACnB,WAAW,EAAE,KAAK,WAAW;MAC7B,SAAS,CACP;OACE,QAAQ;OACR,SAAS;OACV,CACF;MACF;KACF;IACF;GAED,QAAQ,QAAa,SAA+B;IAClD,MAAM,EAAE,QAAQ;IAEhB,MAAM,eAAe,OAAO;IAC5B,MAAM,mBAAmB,KAAK,QAAQ,cAAc,OAAO;IAC3D,MAAM,iBAAiB,cACrB,KAAK,QAAQ,cAAc,eAAe,CAC3C;IAED,MAAM,uBAAuB,aACzB,KAAK,QAAQ,cAAc,WAAW,GACtC,KAAA;IAEJ,MAAM,YAAY,CAChB,GAAI,uBAAuB,CAAC,qBAAqB,GAAG,EAAE,EACtD,GAAG,WAAW,KAAK,QAAQ,KAAK,QAAQ,cAAc,IAAI,CAAC,CAC5D;IAED,MAAM,qBAA4C;KAChD,QAAQ;KACR,cAAc;KACd,GAAI,OAAO,EAAE,MAAM,GAAG,EAAE;KACzB;AAED,QAAI,sBAAsB;KACxB,MAAM,OAAO,WAAW,cAAc,EACpC,aAAa,OACd,CAAC;AAEF,wBAAmB,eAAe;AAChC,aAAO,KAAK,qBAAqB;;eAE1B,YACT,oBAAmB,SAAS;AAG9B,QAAI,UAAU,SAAS,EACrB,oBAAmB,aAAa;IAGlC,MAAM,oBAAoB,CAAC,iBAAiB,mBAAmB;IAE/D,MAAM,eAAe,OAAO,QAAQ,OAAO,MACxC,SACC,KAAK,KAAK,WAAW,kBACrB,KAAK,KAAK,QAAQ,MAAW,EAAE,WAAW,eAAe,CAC5D;AAED,QAAI,cAAc;KAChB,MAAM,WAAW,MAAM,QAAQ,aAAa,IAAI,GAC5C,aAAa,IAAI,MAAM,MAAW,EAAE,WAAW,eAAe,GAC9D,aAAa;AAEjB,SAAI,UAAU,SAAS;AACrB,eAAS,QAAQ,UAAU,SAAS,QAAQ,WAAW,EAAE;AACzD,eAAS,QAAQ,QAAQ,KAAK,kBAAkB;;WAE7C;AACL,YAAO,SAAS,OAAO,UAAU,EAAE;AACnC,YAAO,OAAO,QAAQ,OAAO,OAAO,SAAS,EAAE;AAC/C,YAAO,OAAO,MAAM,KAAK;MACvB,MAAM;MACN,SAAS;MACT,KAAK,CACH;OACE,QAAQ,eAAe,QAAQ,eAAe;OAC9C,SAAS;QACP,SAAS;QACT,YAAY;QACZ,YAAY,EACV,SAAS;SAAC;SAAc;SAAO;SAAoB,EACpD;QACD,SAAS,CAAC,kBAAkB;QAC7B;OACF,CACF;MACF,CAAC;;AAGJ,QAAI,OAAO,WAAW,YAAY,WAChC,QAAO,WAAW,QAAQ,QAAQ,QAAQ;AAG5C,WAAO;;GAEV"}
+{"version":3,"file":"next.js","names":[],"sources":["../../src/zero/next.ts"],"sourcesContent":["/**\n * Next.js configuration wrapper for tasty-zero.\n *\n * Supports both webpack and Turbopack bundlers:\n * - **webpack**: Injects a babel-loader rule with the tasty-zero Babel plugin\n *   via `webpack()` config hook. Config is passed as a jiti factory function.\n * - **Turbopack**: Adds a `turbopack.rules` entry with babel-loader and\n *   JSON-serializable options (`configFile` path instead of a function).\n *   The Babel plugin loads the config internally via jiti.\n *\n * The generated CSS is injected automatically — `@tenphi/tasty/static`\n * imports are replaced with an import of the output CSS file at build time.\n * No manual CSS import in layout files is needed.\n *\n * @example\n * ```javascript\n * // next.config.js\n * const { withTastyZero } = require('@tenphi/tasty/zero/next');\n *\n * module.exports = withTastyZero({\n *   output: 'public/tasty.css',\n *   configFile: './app/tasty-zero.config.ts',\n * })({\n *   // your Next.js config\n * });\n * ```\n */\n\nimport { createRequire } from 'module';\nimport * as path from 'path';\nimport { fileURLToPath } from 'url';\n\nimport { createJiti } from 'jiti';\n\nimport type { TastyZeroBabelOptions, TastyZeroConfig } from './babel';\n\nconst __filename = fileURLToPath(import.meta.url);\nconst __dirname = path.dirname(__filename);\n\n// Next.js types (inline to avoid requiring next as a dependency)\ninterface WebpackConfigContext {\n  isServer: boolean;\n  dev: boolean;\n  buildId: string;\n  dir: string;\n}\n\n/* eslint-disable @typescript-eslint/no-explicit-any -- webpack/Next.js config types are complex */\ninterface TurbopackLoaderItem {\n  loader: string;\n  options?: Record<string, unknown>;\n}\n\ninterface TurbopackRuleConfig {\n  loaders: (string | TurbopackLoaderItem)[];\n  as?: string;\n  condition?: unknown;\n}\n\ninterface TurbopackConfig {\n  rules?: Record<string, TurbopackRuleConfig | TurbopackRuleConfig[]>;\n  [key: string]: unknown;\n}\n\ninterface NextConfig {\n  webpack?: (config: any, context: WebpackConfigContext) => any;\n  turbopack?: TurbopackConfig;\n  [key: string]: unknown;\n}\n\nexport interface TastyZeroNextOptions {\n  /**\n   * Output path for CSS relative to project root.\n   * @default 'public/tasty.css'\n   */\n  output?: string;\n\n  /**\n   * Whether to enable the plugin.\n   * @default true\n   */\n  enabled?: boolean;\n\n  /**\n   * Tasty configuration for build-time processing.\n   * For static configs that don't change during dev.\n   *\n   * For configs that depend on theme files, use `configFile` instead.\n   */\n  config?: TastyZeroConfig;\n\n  /**\n   * Path to a TypeScript/JavaScript module that exports the tasty zero config\n   * as its default export. The module is re-evaluated on each\n   * compilation, enabling hot reload when the file (or its imports) change.\n   *\n   * @example './app/tasty-zero.config.ts'\n   */\n  configFile?: string;\n\n  /**\n   * Extra file paths (relative to project root) that the config depends on.\n   * When any of these files change, the Babel cache is invalidated and\n   * the config is re-evaluated.\n   *\n   * The `configFile` itself is always tracked automatically.\n   * Use this for transitive dependencies that aren't directly imported\n   * by the config file, or when using `config` instead of `configFile`.\n   *\n   * @example ['./app/theme.ts']\n   */\n  configDeps?: string[];\n\n  /**\n   * Output mode for extracted CSS.\n   *\n   * - `'file'` (default): CSS is written to a single output file.\n   * - `'inject'`: CSS is embedded inline in JS and injected at runtime.\n   *   No CSS file is written. Best for reusable components and extensions.\n   *\n   * When `mode` is `'inject'`, `output` is ignored.\n   *\n   * @default 'file'\n   */\n  mode?: 'file' | 'inject';\n}\n\n/**\n * Next.js configuration wrapper for tasty-zero.\n * Configures both webpack and Turbopack bundlers automatically.\n */\nexport function withTastyZero(options: TastyZeroNextOptions = {}) {\n  const {\n    output = 'public/tasty.css',\n    enabled = true,\n    config: tastyConfig,\n    configFile,\n    configDeps = [],\n    mode,\n  } = options;\n\n  return (nextConfig: NextConfig = {}): NextConfig => {\n    if (!enabled) {\n      return nextConfig;\n    }\n\n    const projectDir = process.cwd();\n    const absoluteOutput = path.resolve(projectDir, output);\n    const babelPluginPath = path.resolve(__dirname, 'babel.js');\n\n    const absoluteConfigFile = configFile\n      ? path.resolve(projectDir, configFile)\n      : undefined;\n\n    const allDeps = [\n      ...(absoluteConfigFile ? [absoluteConfigFile] : []),\n      ...configDeps.map((dep) => path.resolve(projectDir, dep)),\n    ];\n\n    // --- Turbopack configuration ---\n    // Turbopack loader options must be JSON-serializable (no functions).\n    // The Babel plugin loads config internally via `configFile` path + jiti.\n    const turbopackBabelOptions: Record<string, unknown> = {\n      babelrc: false,\n      configFile: false,\n      parserOpts: {\n        plugins: ['typescript', 'jsx', 'decorators-legacy'],\n      },\n      plugins: [\n        [\n          babelPluginPath,\n          {\n            output: absoluteOutput,\n            injectImport: true,\n            ...(mode ? { mode } : {}),\n            ...(absoluteConfigFile\n              ? { configFile: absoluteConfigFile }\n              : tastyConfig\n                ? { config: tastyConfig }\n                : {}),\n            ...(allDeps.length > 0 ? { configDeps: allDeps } : {}),\n          },\n        ],\n      ],\n    };\n\n    const existingTurbopack = nextConfig.turbopack || {};\n    const existingRules = existingTurbopack.rules || {};\n\n    const existingExperimental =\n      (nextConfig.experimental as Record<string, unknown>) || {};\n\n    return {\n      ...nextConfig,\n\n      experimental: {\n        ...existingExperimental,\n        turbopackUseBuiltinBabel: true,\n      },\n\n      turbopack: {\n        ...existingTurbopack,\n        rules: {\n          ...existingRules,\n          '*.{ts,tsx,js,jsx}': {\n            condition: { not: 'foreign' },\n            loaders: [\n              {\n                loader: 'babel-loader',\n                options: turbopackBabelOptions,\n              },\n            ],\n          },\n        },\n      },\n\n      webpack(config: any, context: WebpackConfigContext) {\n        const { dir } = context;\n\n        const wpProjectDir = dir || projectDir;\n        const wpAbsoluteOutput = path.resolve(wpProjectDir, output);\n        const projectRequire = createRequire(\n          path.resolve(wpProjectDir, 'package.json'),\n        );\n\n        const wpAbsoluteConfigFile = configFile\n          ? path.resolve(wpProjectDir, configFile)\n          : undefined;\n\n        const wpAllDeps = [\n          ...(wpAbsoluteConfigFile ? [wpAbsoluteConfigFile] : []),\n          ...configDeps.map((dep) => path.resolve(wpProjectDir, dep)),\n        ];\n\n        const babelPluginOptions: TastyZeroBabelOptions = {\n          output: wpAbsoluteOutput,\n          injectImport: true,\n          ...(mode ? { mode } : {}),\n        };\n\n        if (wpAbsoluteConfigFile) {\n          const jiti = createJiti(wpProjectDir, {\n            moduleCache: false,\n          });\n\n          babelPluginOptions.config = () => {\n            return jiti(wpAbsoluteConfigFile) as TastyZeroConfig;\n          };\n        } else if (tastyConfig) {\n          babelPluginOptions.config = tastyConfig;\n        }\n\n        if (wpAllDeps.length > 0) {\n          babelPluginOptions.configDeps = wpAllDeps;\n        }\n\n        const babelPluginConfig = [babelPluginPath, babelPluginOptions];\n\n        const existingRule = config.module?.rules?.find(\n          (rule: any) =>\n            rule.use?.loader === 'babel-loader' ||\n            rule.use?.some?.((u: any) => u.loader === 'babel-loader'),\n        );\n\n        if (existingRule) {\n          const babelUse = Array.isArray(existingRule.use)\n            ? existingRule.use.find((u: any) => u.loader === 'babel-loader')\n            : existingRule.use;\n\n          if (babelUse?.options) {\n            babelUse.options.plugins = babelUse.options.plugins || [];\n            babelUse.options.plugins.push(babelPluginConfig);\n          }\n        } else {\n          config.module = config.module || {};\n          config.module.rules = config.module.rules || [];\n          config.module.rules.push({\n            test: /\\.(tsx?|jsx?)$/,\n            exclude: /node_modules/,\n            use: [\n              {\n                loader: projectRequire.resolve('babel-loader'),\n                options: {\n                  babelrc: false,\n                  configFile: false,\n                  parserOpts: {\n                    plugins: ['typescript', 'jsx', 'decorators-legacy'],\n                  },\n                  plugins: [babelPluginConfig],\n                },\n              },\n            ],\n          });\n        }\n\n        if (typeof nextConfig.webpack === 'function') {\n          return nextConfig.webpack(config, context);\n        }\n\n        return config;\n      },\n    };\n  };\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAoCA,MAAM,aAAa,cAAc,OAAO,KAAK,GAAG;AAChD,MAAM,YAAY,KAAK,QAAQ,UAAU;;;;;AA8FzC,SAAgB,cAAc,UAAgC,CAAC,GAAG;CAChE,MAAM,EACJ,SAAS,oBACT,UAAU,MACV,QAAQ,aACR,YACA,aAAa,CAAC,GACd,SACE;CAEJ,QAAQ,aAAyB,CAAC,MAAkB;EAClD,IAAI,CAAC,SACH,OAAO;EAGT,MAAM,aAAa,QAAQ,IAAI;EAC/B,MAAM,iBAAiB,KAAK,QAAQ,YAAY,MAAM;EACtD,MAAM,kBAAkB,KAAK,QAAQ,WAAW,UAAU;EAE1D,MAAM,qBAAqB,aACvB,KAAK,QAAQ,YAAY,UAAU,IACnC,KAAA;EAEJ,MAAM,UAAU,CACd,GAAI,qBAAqB,CAAC,kBAAkB,IAAI,CAAC,GACjD,GAAG,WAAW,KAAK,QAAQ,KAAK,QAAQ,YAAY,GAAG,CAAC,CAC1D;EAKA,MAAM,wBAAiD;GACrD,SAAS;GACT,YAAY;GACZ,YAAY,EACV,SAAS;IAAC;IAAc;IAAO;GAAmB,EACpD;GACA,SAAS,CACP,CACE,iBACA;IACE,QAAQ;IACR,cAAc;IACd,GAAI,OAAO,EAAE,KAAK,IAAI,CAAC;IACvB,GAAI,qBACA,EAAE,YAAY,mBAAmB,IACjC,cACE,EAAE,QAAQ,YAAY,IACtB,CAAC;IACP,GAAI,QAAQ,SAAS,IAAI,EAAE,YAAY,QAAQ,IAAI,CAAC;GACtD,CACF,CACF;EACF;EAEA,MAAM,oBAAoB,WAAW,aAAa,CAAC;EACnD,MAAM,gBAAgB,kBAAkB,SAAS,CAAC;EAElD,MAAM,uBACH,WAAW,gBAA4C,CAAC;EAE3D,OAAO;GACL,GAAG;GAEH,cAAc;IACZ,GAAG;IACH,0BAA0B;GAC5B;GAEA,WAAW;IACT,GAAG;IACH,OAAO;KACL,GAAG;KACH,qBAAqB;MACnB,WAAW,EAAE,KAAK,UAAU;MAC5B,SAAS,CACP;OACE,QAAQ;OACR,SAAS;MACX,CACF;KACF;IACF;GACF;GAEA,QAAQ,QAAa,SAA+B;IAClD,MAAM,EAAE,QAAQ;IAEhB,MAAM,eAAe,OAAO;IAC5B,MAAM,mBAAmB,KAAK,QAAQ,cAAc,MAAM;IAC1D,MAAM,iBAAiB,cACrB,KAAK,QAAQ,cAAc,cAAc,CAC3C;IAEA,MAAM,uBAAuB,aACzB,KAAK,QAAQ,cAAc,UAAU,IACrC,KAAA;IAEJ,MAAM,YAAY,CAChB,GAAI,uBAAuB,CAAC,oBAAoB,IAAI,CAAC,GACrD,GAAG,WAAW,KAAK,QAAQ,KAAK,QAAQ,cAAc,GAAG,CAAC,CAC5D;IAEA,MAAM,qBAA4C;KAChD,QAAQ;KACR,cAAc;KACd,GAAI,OAAO,EAAE,KAAK,IAAI,CAAC;IACzB;IAEA,IAAI,sBAAsB;KACxB,MAAM,OAAO,WAAW,cAAc,EACpC,aAAa,MACf,CAAC;KAED,mBAAmB,eAAe;MAChC,OAAO,KAAK,oBAAoB;KAClC;IACF,OAAO,IAAI,aACT,mBAAmB,SAAS;IAG9B,IAAI,UAAU,SAAS,GACrB,mBAAmB,aAAa;IAGlC,MAAM,oBAAoB,CAAC,iBAAiB,kBAAkB;IAE9D,MAAM,eAAe,OAAO,QAAQ,OAAO,MACxC,SACC,KAAK,KAAK,WAAW,kBACrB,KAAK,KAAK,QAAQ,MAAW,EAAE,WAAW,cAAc,CAC5D;IAEA,IAAI,cAAc;KAChB,MAAM,WAAW,MAAM,QAAQ,aAAa,GAAG,IAC3C,aAAa,IAAI,MAAM,MAAW,EAAE,WAAW,cAAc,IAC7D,aAAa;KAEjB,IAAI,UAAU,SAAS;MACrB,SAAS,QAAQ,UAAU,SAAS,QAAQ,WAAW,CAAC;MACxD,SAAS,QAAQ,QAAQ,KAAK,iBAAiB;KACjD;IACF,OAAO;KACL,OAAO,SAAS,OAAO,UAAU,CAAC;KAClC,OAAO,OAAO,QAAQ,OAAO,OAAO,SAAS,CAAC;KAC9C,OAAO,OAAO,MAAM,KAAK;MACvB,MAAM;MACN,SAAS;MACT,KAAK,CACH;OACE,QAAQ,eAAe,QAAQ,cAAc;OAC7C,SAAS;QACP,SAAS;QACT,YAAY;QACZ,YAAY,EACV,SAAS;SAAC;SAAc;SAAO;QAAmB,EACpD;QACA,SAAS,CAAC,iBAAiB;OAC7B;MACF,CACF;KACF,CAAC;IACH;IAEA,IAAI,OAAO,WAAW,YAAY,YAChC,OAAO,WAAW,QAAQ,QAAQ,OAAO;IAG3C,OAAO;GACT;EACF;CACF;AACF"}

package/docs/README.md

@@ -1,31 +1,39 @@
 # Tasty Docs
 
-Tasty is a styling engine for design systems that turns component state into deterministic CSS by compiling state maps into mutually exclusive selectors. Use this hub to choose the right guide once you know whether you are evaluating the model, adopting it in a design system, or implementing reusable, stateful components day to day.
+Tasty is CSS-in-JS for React design systems. You describe hover, disabled, variants, themes, responsive behavior, and other conditions as state maps; Tasty compiles them so one branch wins without specificity fights or source-order surprises.
+
+Use this hub to move from the core idea to a working component, then into design-system patterns or API reference as needed.
 
 ## Start Here
 
-- **New to Tasty**: [Getting Started](getting-started.md) for installation, the first component, optional shared `configure()`, ESLint, editor tooling, and rendering mode selection.
-- **Learning the component model**: [Methodology](methodology.md) for root + sub-elements, `styleProps`, tokens, extension, and recommended boundaries between `styles`, `style`, and wrappers.
-- **Evaluating the selector model**: [Style rendering pipeline](PIPELINE.md) for how mutually exclusive selectors make stateful styling deterministic.
-- **Evaluating fit**: [Comparison](comparison.md) for tool-selection context, then [Adoption Guide](adoption.md) for audience fit and rollout strategy inside a design system.
+- **Understand why**: [Introduction](../README.md) for the problem, the state-map model, and the product overview.
+- **Try it**: [Getting Started](getting-started.md) to build a stateful component, add shared configuration, and choose a rendering mode.
+- **Build a component system**: [Methodology](methodology.md) for root + sub-elements, typed public APIs, tokens, and extension patterns; then [Building a Design System](design-system.md).
+- **Evaluate or adopt it**: [Comparison](comparison.md) for tool-selection context and [Adoption Guide](adoption.md) for an incremental rollout.
+- **Understand the compiler**: [Style rendering pipeline](pipeline.md) for how state maps become mutually exclusive selectors.
 
 ## By Role
 
 - **Application developer using an existing design system**: [Getting Started](getting-started.md), then [React API](react-api.md).
 - **Design-system author**: [Methodology](methodology.md), [Building a Design System](design-system.md), [Configuration](configuration.md), and [Adoption Guide](adoption.md).
-- **Platform or tooling engineer**: [Configuration](configuration.md), [Zero Runtime (tastyStatic)](tasty-static.md), [Server-Side Rendering](ssr.md), and [Debug Utilities](debug.md).
+- **Platform or tooling engineer**: [Configuration](configuration.md), [Build-Time Extraction (`tastyStatic`)](tasty-static.md), [Server-Side Rendering](ssr.md), and [Debug Utilities](debug.md).
 
 ## By Styling Approach
 
 - **React components**: [React API](react-api.md)
-- **Zero-runtime / build-time extraction**: [Zero Runtime (tastyStatic)](tasty-static.md)
-- **Runtime `tasty()` with server collection and hydration**: [Server-Side Rendering](ssr.md)
+- **Zero-client-runtime React with `tasty()`**: [Server-Side Rendering](ssr.md), especially the static Astro integration
+- **Build-time extraction with `tastyStatic()`**: [Build-Time Extraction](tasty-static.md)
+- **Hydrated `tasty()` with server collection**: [Server-Side Rendering](ssr.md)
+- **Upgrading from v2**: [Migration Guide (v2 → v3)](migration-v3.md)
 
 ## By Task
 
 - **Learn the style language**: [Style DSL](dsl.md)
+- **Brief an AI agent (or yourself) on writing correct styles**: [Style Rules for AI Agents](ai-agents.md)
 - **Look up a property handler**: [Style Properties](styles.md)
-- **Define tokens, units, recipes, keyframes, or properties globally**: [Configuration](configuration.md)
+- **Define tokens, units, recipes, keyframes, properties, functions, or polyfills globally**: [Configuration](configuration.md)
+- **Extend Tasty with a plugin, custom handler, or custom prop**: [Plugins & Extension Points](plugins.md)
 - **Debug generated CSS or cache behavior**: [Debug Utilities](debug.md)
-- **Understand how selector generation works internally**: [Style rendering pipeline](PIPELINE.md)
+- **Understand how selector generation works internally**: [Style rendering pipeline](pipeline.md)
 - **Understand runtime injection internals**: [Style Injector](injector.md)
+- **Reproduce and interpret performance measurements**: [Runtime Benchmarks](runtime-benchmarks.md)

package/docs/adoption.md

@@ -1,8 +1,10 @@
 # Adoption Guide
 
-Tasty is not a drop-in replacement for another styling library. It is a **substrate for building a design-system-defined styling language**: what the comparison guide calls a house styling language. That means adoption usually starts where styling for reusable, stateful components has already become a composition problem, not with an all-at-once rewrite.
+Tasty is most useful where reusable component styling has become a state-resolution problem: hover intersects with disabled, variants intersect with themes, and every extension makes selector behavior harder to predict.
 
-This guide is for design-system maintainers and platform engineers evaluating Tasty or introducing it into an existing codebase. Use this document for rollout strategy and adoption sequencing; use the [Comparison guide](comparison.md) when the open question is whether Tasty is the right tool in the first place.
+It normally sits underneath a design system’s existing components. You can preserve their public React APIs while moving their style logic into state maps that produce one declared winner. Adoption should start with a small, state-heavy component—not an all-at-once rewrite.
+
+This guide is for design-system maintainers and platform engineers evaluating Tasty or introducing it into an existing codebase. Use it for rollout strategy and adoption sequencing; use the [Comparison guide](comparison.md) when the open question is whether Tasty is the right tool.
 
 ---
 
@@ -18,12 +20,14 @@ Product code
 ```
 
 **What Tasty owns:**
+
 - The DSL and value parser (tokens, custom units, auto-calc, color opacity)
 - State compilation (mutually exclusive selectors from state maps)
 - Style injection and deduplication (runtime or build-time)
 - The `tasty()` component factory and hooks API
 
 **What the DS team owns:**
+
 - Token names and values (colors, spacing, typography)
 - Custom units and their semantics
 - State aliases (`@mobile`, `@dark`, `@compact`)
@@ -39,12 +43,14 @@ Two teams using Tasty can end up with very different authoring models. That is b
 ## Who should adopt Tasty
 
 **Strong fit:**
-- A design-system or platform team that wants to define a governed styling language
+
+- A design-system or platform team that owns shared component APIs
 - Components with complex, intersecting states (hover + disabled + theme + breakpoint)
 - Teams that need deterministic style resolution without cascade/specificity bugs
-- Organizations where styling decisions should be centralized, not distributed
+- Organizations that want tokens, states, and extension rules to stay consistent across products
 
 **Not the right fit:**
+
 - Solo developers building a one-off app with minimal UI structure
 - Teams that want a shared utility vocabulary and direct markup authoring (Tailwind is better here)
 - Projects where low ceremony matters more than central governance
@@ -58,16 +64,16 @@ For a detailed comparison with Tailwind, Panda CSS, vanilla-extract, StyleX, Sti
 
 Tasty provides the engine. The DS team defines the language that runs on it. Here is what that typically involves:
 
-| Layer | What you define | Where |
-|-------|----------------|-------|
-| **Tokens** | Color names, spacing scale, border widths, radii | `configure({ tokens })` |
-| **Units** | Custom multiplier units (`x`, `r`, `bw`, or your own) | `configure({ units })` |
-| **State aliases** | Responsive breakpoints, theme modes, feature flags | `configure({ states })` |
-| **Recipes** | Reusable style bundles (card, elevated, input-reset) | `configure({ recipes })` |
-| **Typography** | Preset definitions (h1-h6, t1-t4, etc.) | `configure({ presets: { ... } })` |
-| **Style props** | Which CSS properties each component exposes as React props | `styleProps` in each component |
-| **Sub-elements** | Inner parts of compound components (Title, Icon, Content) | `elements` + capitalized keys in `styles` |
-| **Override rules** | How product engineers extend or constrain components | Styled wrappers via `tasty(Base, { ... })` |
+| Layer              | What you define                                            | Where                                      |
+| ------------------ | ---------------------------------------------------------- | ------------------------------------------ |
+| **Tokens**         | Color names, spacing scale, border widths, radii           | `configure({ tokens })`                    |
+| **Units**          | Custom multiplier units (`x`, `r`, `bw`, or your own)      | `configure({ units })`                     |
+| **State aliases**  | Responsive breakpoints, theme modes, feature flags         | `configure({ states })`                    |
+| **Recipes**        | Reusable style bundles (card, elevated, input-reset)       | `configure({ recipes })`                   |
+| **Typography**     | Preset definitions (h1-h6, t1-t4, etc.)                    | `configure({ presets: { ... } })`          |
+| **Style props**    | Which CSS properties each component exposes as React props | `styleProps` in each component             |
+| **Sub-elements**   | Inner parts of compound components (Title, Icon, Content)  | `elements` + capitalized keys in `styles`  |
+| **Override rules** | How product engineers extend or constrain components       | Styled wrappers via `tasty(Base, { ... })` |
 
 The same engine can power a minimal design system with a handful of tokens:
 
@@ -85,9 +91,15 @@ Here is how the layers connect end-to-end. The DS team configures the engine, de
 ```tsx
 // ds/config.ts — DS team defines the language
 configure({
-  tokens: { '#primary': 'oklch(55% 0.25 265)', '#surface': '#fff', '#text': '#111' },
+  tokens: {
+    '#primary': 'oklch(55% 0.25 265)',
+    '#surface': '#fff',
+    '#text': '#111',
+  },
   states: { '@mobile': '@media(w < 768px)', '@dark': '@root(schema=dark)' },
-  recipes: { card: { padding: '4x', fill: '#surface', radius: '1r', border: true } },
+  recipes: {
+    card: { padding: '4x', fill: '#surface', radius: '1r', border: true },
+  },
 });
 
 // ds/components/Card.tsx — DS team builds components on top
@@ -105,7 +117,7 @@ const Card = tasty({
 <Card padding={{ '': '4x', '@mobile': '2x' }}>
   <Card.Title>Monthly Revenue</Card.Title>
   <Card.Body>$1.2M — up 12% from last month</Card.Body>
-</Card>
+</Card>;
 ```
 
 See [Configuration](configuration.md) for the full `configure()` API.
@@ -116,9 +128,21 @@ See [Configuration](configuration.md) for the full `configure()` API.
 
 You do not need to adopt everything at once. Tasty is designed to be introduced layer by layer.
 
-A practical way to start is with the components that already suffer from intersecting state and variant logic: buttons, inputs, menus, disclosures, dialogs, list items, interactive cards, and compound components. Those are the places where deterministic resolution pays off fastest.
+A practical first slice is one component that already suffers from intersecting state and variant logic: a button, input, menu item, disclosure, or interactive card. Keep its public API unchanged, move one or two properties into Tasty state maps, and verify that the declared priority matches the behavior your team expects.
+
+This proves the differentiator before you invest in a complete token vocabulary or migrate an entire component library.
+
+### Phase 1 -- Pilot one state-heavy component
+
+Choose a component with a known hover/disabled, focus/error, or variant/theme interaction. Preserve its external props and visual behavior. The pilot should answer three questions:
+
+1. Is the state map easier to review than the existing selectors or conditional class logic?
+2. Does extending the component keep the intended state priority?
+3. Can your current tokens and component API move over without product-code churn?
+
+If the answer is yes, establish the shared design-system vocabulary around the successful slice.
 
-### Phase 1 -- Tokens and units
+### Phase 2 -- Tokens and units
 
 Start by defining your design tokens and custom units. This is the lowest-risk step: it only configures the parser and does not require rewriting any components.
 
@@ -136,14 +160,14 @@ configure({
   // A DS typically redefines them to use CSS custom properties
   // so that the actual scale is controlled via CSS, not JS:
   units: {
-    x: 'var(--gap)',   // 2x → calc(var(--gap) * 2)
+    x: 'var(--gap)', // 2x → calc(var(--gap) * 2)
     r: 'var(--radius)',
     bw: 'var(--border-width)',
   },
 });
 ```
 
-### Phase 2 -- State aliases and recipes
+### Phase 3 -- State aliases and recipes
 
 Define the state vocabulary your components will share. This is where you start encoding your team's conventions.
 
@@ -152,7 +176,8 @@ configure({
   states: {
     '@mobile': '@media(w < 768px)',
     '@tablet': '@media(w < 1024px)',
-    '@dark': '@root(schema=dark) | (!@root(schema) & @media(prefers-color-scheme: dark))',
+    '@dark':
+      '@root(schema=dark) | (!@root(schema) & @media(prefers-color-scheme: dark))',
   },
   recipes: {
     card: { padding: '4x', fill: '#surface', radius: '1r', border: true },
@@ -161,7 +186,7 @@ configure({
 });
 ```
 
-### Phase 3 -- Migrate a few primitives
+### Phase 4 -- Migrate a few primitives
 
 Pick 2-3 widely used primitives (Box, Text, Button) and rewrite them with `tasty()`. Keep the public API identical so product code does not need to change.
 
@@ -179,7 +204,7 @@ const Box = tasty({
 
 At this point you can validate the DSL, token workflow, and component authoring experience before expanding the rollout.
 
-### Phase 4 -- Encode complex states
+### Phase 5 -- Expand state resolution
 
 Move the components with the most painful intersecting states (buttons with hover + disabled + theme variants, inputs with focus + error + readonly) to Tasty's state map syntax. This is where mutually exclusive selectors start paying off.
 
@@ -209,7 +234,7 @@ const Button = tasty({
 });
 ```
 
-### Phase 5 -- Standardize style props and sub-elements
+### Phase 6 -- Standardize style props and sub-elements
 
 Define which style props each component category exposes. Layout components get flow/gap/padding. Interactive components get positioning. Compound components declare sub-elements.
 
@@ -225,9 +250,9 @@ const Card = tasty({
 });
 ```
 
-### Phase 6 -- Expand to full DS coverage
+### Phase 7 -- Expand to full DS coverage
 
-Migrate the remaining components, add the [ESLint plugin](https://github.com/tenphi/eslint-plugin-tasty) to enforce style conventions at lint time, and consider [zero-runtime mode](tasty-static.md) for static or performance-critical pages.
+Migrate the remaining components, add the [ESLint plugin](https://github.com/tenphi/eslint-plugin-tasty) to enforce style conventions at lint time, and choose between [server-only `tasty()`](ssr.md) and [`tastyStatic()` build-time extraction](tasty-static.md) when a page should ship no Tasty styling runtime.
 
 ---
 
@@ -254,8 +279,8 @@ const DangerButton = tasty(Button, {
 const LoadingButton = tasty(Button, {
   styles: {
     fill: {
-      loading: '#yellow',       // new state appended
-      disabled: '#gray.20',     // existing state overridden in place
+      loading: '#yellow', // new state appended
+      disabled: '#gray.20', // existing state overridden in place
     },
   },
 });
@@ -270,7 +295,7 @@ const LoadingButton = tasty(Button, {
 </Space>
 ```
 
-**Components are server components by default.** All `tasty()` components and style functions are hook-free, so they work as React Server Components without `'use client'`. In server-only contexts (Next.js RSC, Astro without `client:*` directives), they produce zero client JavaScript. Product engineers only add `'use client'` when their component needs actual React interactivity (state, effects, event handlers), never because of styling.
+**Components are server components by default.** All `tasty()` components and style functions are hook-free, so they work as React Server Components without `'use client'`. In server-only contexts they ship no Tasty styling runtime. Astro without `client:*` directives ships no client JavaScript; server-only Next.js RSC follows the same Tasty architecture, while final output depends on the application deployment. Product engineers only add `'use client'` when their component needs actual React interactivity (state, effects, event handlers), never because of styling.
 
 **No cascade/specificity concerns.** Tasty's mutually exclusive selectors mean extending a component cannot accidentally break another. Import order, class name collisions, and specificity arithmetic are non-issues.
 
@@ -295,4 +320,4 @@ const LoadingButton = tasty(Button, {
 - [Configuration](configuration.md) -- tokens, recipes, custom units, style handlers, and TypeScript extensions
 - [Style Properties](styles.md) -- complete reference for all enhanced style properties
 - [Comparison](comparison.md) -- positioning and trade-offs vs. other styling systems
-- [Zero Runtime (tastyStatic)](tasty-static.md) -- build-time static styling with Babel plugin
+- [Build-Time Extraction (`tastyStatic`)](tasty-static.md) -- static styling with the Babel plugin