@epilot/volt-ui-experimental-griffel 0.2.0 → 0.2.3

package/dist/tokens/install.js.map

@@ -1 +1 @@
-{"version":3,"file":"install.js","sources":["../../src/tokens/install.ts"],"sourcesContent":["import { ensureSheet, __resetInstalledSheets } from \"@epilot/volt-ui-runtime\"\nimport { CSS as CORE_CSS, SHEET_HASH as CORE_HASH } from \"./core.generated\"\nimport {\n  CSS as PALETTE_CSS,\n  SHEET_HASH as PALETTE_HASH,\n} from \"./palette.generated\"\n\n/**\n * Token sheet delivery.\n *\n * Each sheet is keyed by the hash of its own CONTENT, so N copies of the same version insert it\n * once, and two builds with different token values coexist as two sheets. Crucially, the values\n * cannot fight: property NAMES carry a value-derived namespace segment, so different values mean\n * different names. That is what lets both sheets sit on `:root` — the PoC originally salted only\n * the CLASS namespace and measured exactly this defect, with two divergent builds rendering the\n * same colour and the winner decided by MFE load order.\n *\n * Two sheets rather than one, per DECISIONS.md D5. Core carries the semantic layer for the intent\n * families plus the owned scale; palette carries the decorative families, which are reachable only\n * through a consumer-facing `color` prop. `ensurePalette()` is called by the components that expose\n * one, so a consumer using only Dialog, Field and Tooltip never ships or inserts it.\n *\n * The PoC also modelled a `host` delivery variant — root-config ships the sheet, like today's\n * singleton `style.css` link. Not carried: it reintroduces the failure this architecture exists to\n * remove (a missing or stale host sheet unstyles every v2 MFE at once) and it requires a breaking\n * host change deployed ahead of the package.\n *\n * Note what did NOT move when the engine did. `ensureSheet` is the runtime's, because placement is\n * anchor-relative and the anchor is shared. The CSS below is this package's, because it is exactly\n * the thing that must differ between two co-resident versions. That is the same line the `host`\n * variant above got wrong, drawn one level further in.\n */\n\n/** Test-only: forget what this module thinks it has installed. */\nexport function __resetTokensForTests(): void {\n  __resetInstalledSheets()\n}\n\nexport function ensureCoreTokens(doc: Document = document): boolean {\n  return ensureSheet(doc, CORE_HASH, CORE_CSS)\n}\n\n/**\n * Called by components that accept a `color` prop, since a decorative family can arrive from a\n * runtime expression the build cannot see — `getColorForEntityLabel(label)` and\n * `WCAG_BADGE_MAP[level].color` both exist in consumer code today.\n */\nexport function ensurePaletteTokens(doc: Document = document): boolean {\n  return ensureSheet(doc, PALETTE_HASH, PALETTE_CSS)\n}\n\nexport const TOKEN_SHEET_HASHES = {\n  core: CORE_HASH,\n  palette: PALETTE_HASH,\n} as const\n"],"names":["ensureCoreTokens","doc","ensureSheet","CORE_HASH","CORE_CSS","ensurePaletteTokens","PALETTE_HASH","PALETTE_CSS"],"mappings":";;;AAsCO,SAASA,EAAiBC,IAAgB,UAAmB;AAClE,SAAOC,EAAYD,GAAKE,GAAWC,CAAQ;AAC7C;AAOO,SAASC,EAAoBJ,IAAgB,UAAmB;AACrE,SAAOC,EAAYD,GAAKK,GAAcC,CAAW;AACnD;"}
+{"version":3,"file":"install.js","sources":["../../src/tokens/install.ts"],"sourcesContent":["import { ensureSheet, __resetInstalledSheets } from \"@epilot/volt-ui-runtime\"\nimport { CSS as CORE_CSS, SHEET_HASH as CORE_HASH } from \"./core.generated\"\nimport {\n  CSS as PALETTE_CSS,\n  SHEET_HASH as PALETTE_HASH,\n} from \"./palette.generated\"\n\n/**\n * Token sheet delivery.\n *\n * Each sheet is keyed by the hash of its own CONTENT, so N copies of the same version insert it\n * once, and two builds with different token values coexist as two sheets. Crucially, the values\n * cannot fight: property NAMES carry a value-derived namespace segment, so different values mean\n * different names. That is what lets both sheets sit on `:root` — the PoC originally salted only\n * the CLASS namespace and measured exactly this defect, with two divergent builds rendering the\n * same colour and the winner decided by MFE load order.\n *\n * Two sheets rather than one, per DECISIONS.md D5. Core carries the semantic layer for the intent\n * families plus the owned scale; palette carries the decorative families, which are reachable only\n * through a consumer-facing `color` prop. `ensurePalette()` is called by the components that expose\n * one, so a consumer using only Dialog, Field and Tooltip never ships or inserts it.\n *\n * The PoC also modelled a `host` delivery variant — root-config ships the sheet, like today's\n * singleton `style.css` link. Not carried: it reintroduces the failure this architecture exists to\n * remove (a missing or stale host sheet unstyles every v2 MFE at once) and it requires a breaking\n * host change deployed ahead of the package.\n *\n * Note what did NOT move when the engine did. `ensureSheet` is the runtime's, because placement is\n * anchor-relative and the anchor is shared. The CSS below is this package's, because it is exactly\n * the thing that must differ between two co-resident versions. That is the same line the `host`\n * variant above got wrong, drawn one level further in.\n */\n\n/** Test-only: forget what this module thinks it has installed. */\nexport function __resetTokensForTests(): void {\n  __resetInstalledSheets()\n}\n\nexport function ensureCoreTokens(doc: Document = document): boolean {\n  return ensureSheet(doc, CORE_HASH, CORE_CSS)\n}\n\n/**\n * Called by components that accept a `color` prop, since a decorative family can arrive from a\n * runtime expression the build cannot see — `getColorForEntityLabel(label)` and\n * `WCAG_BADGE_MAP[level].color` both exist in consumer code today.\n */\nexport function ensurePaletteTokens(doc: Document = document): boolean {\n  return ensureSheet(doc, PALETTE_HASH, PALETTE_CSS)\n}\n\n/**\n * The families the CORE sheet declares. Everything else is decorative and lives in the palette\n * sheet. `core-families.test.ts` asserts this list against the generated sheets in both directions, so a\n * family moving between them cannot silently invalidate the check below.\n */\nconst CORE_FAMILIES = new Set([\n  \"accent\",\n  \"gray\",\n  \"error\",\n  \"info\",\n  \"success\",\n  \"warning\",\n])\n\n/**\n * Install the palette sheet only if this family actually needs it.\n *\n * The unconditional call was measured as the single most expensive thing a `color`-prop component\n * does: the palette sheet is 63,689 B of CSS, and a differential build put `Pill`'s marginal cost at\n * 69,087 B raw against `Button`'s 6,330 B. The flows pilot separately measured 69,787 B of runtime\n * token CSS in the document for a two-component consumer, 18× the 3,814 B of actual atoms.\n *\n * Passing the resolved family keeps the correctness the unconditional call was protecting. The\n * hazard it guarded against is a family arriving from an expression the BUILD cannot see; by render\n * time the value is in hand, so a dynamic `getColorForEntityLabel(label)` that returns `teal` still\n * installs the sheet before paint. What goes away is installing it for `accent` or `gray`.\n *\n * This does NOT reduce bundle size. `ensurePaletteTokens` stays referenced, so the sheet is still\n * emitted into any chunk that contains one of these components — cutting that needs build-time\n * knowledge of which families a consumer uses, which the package cannot have. See DECISIONS D14.\n */\nexport function ensurePaletteTokensFor(\n  family: string,\n  doc: Document = document\n): boolean {\n  if (CORE_FAMILIES.has(family)) return false\n\n  return ensurePaletteTokens(doc)\n}\n\nexport const TOKEN_SHEET_HASHES = {\n  core: CORE_HASH,\n  palette: PALETTE_HASH,\n} as const\n"],"names":["ensureCoreTokens","doc","ensureSheet","CORE_HASH","CORE_CSS","ensurePaletteTokens","PALETTE_HASH","PALETTE_CSS","CORE_FAMILIES","ensurePaletteTokensFor","family"],"mappings":";;;AAsCO,SAASA,EAAiBC,IAAgB,UAAmB;AAClE,SAAOC,EAAYD,GAAKE,GAAWC,CAAQ;AAC7C;AAOO,SAASC,EAAoBJ,IAAgB,UAAmB;AACrE,SAAOC,EAAYD,GAAKK,GAAcC,CAAW;AACnD;AAOA,MAAMC,wBAAoB,IAAI;AAAA,EAC5B;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AAAA,EACA;AACF,CAAC;AAmBM,SAASC,EACdC,GACAT,IAAgB,UACP;AACT,SAAIO,EAAc,IAAIE,CAAM,IAAU,KAE/BL,EAAoBJ,CAAG;AAChC;"}