@kong/design-tokens 2.0.1-pr.670.ff5aeec.0 → 2.0.1

package/README.md

@@ -2,11 +2,6 @@
 
 Kong Design Tokens for Konnect, via [Style Dictionary](https://github.com/amzn/style-dictionary).
 
-- [Token Tiers](#token-tiers)
-  - [Semantic tokens](#semantic-tokens)
-  - [Component tokens — names only, value-less](#component-tokens--names-only-value-less)
-  - [Themeable token list](#themeable-token-list)
-- [Themes](#themes)
 - [Tokens](#tokens)
   - [Token Formats](#token-formats)
   - [SCSS](#scss)
@@ -17,12 +12,8 @@ Kong Design Tokens for Konnect, via [Style Dictionary](https://github.com/amzn/s
   - [Installation](#installation)
   - [Standalone components](#standalone-components)
   - [Host applications](#host-applications)
-  - [Kongponents](#kongponents)
 - [Updating Tokens & Local Development](#updating-tokens--local-development)
-  - [Directory structure](#directory-structure)
   - [Token Requirements](#token-requirements)
-  - [Creating a new theme](#creating-a-new-theme)
-  - [Theme `$description` authoring rules](#theme-description-authoring-rules)
   - [Development Sandbox](#development-sandbox)
   - [Lint and fix](#lint-and-fix)
   - [Build for production](#build-for-production)
@@ -31,88 +22,10 @@ Kong Design Tokens for Konnect, via [Style Dictionary](https://github.com/amzn/s
   - [Approvals](#approvals)
   - [Package Publishing](#package-publishing)
 
-## Token Tiers
-
-The `@kong/design-tokens` package uses a two-tier exported token taxonomy.
-
-| Tier | Source directory | Examples | Exported as |
-|------|-----------------|----------|-------------|
-| **Semantic** | `tokens/source/**` | `--kui-color-background-primary`, `--kui-space-40`, `--kui-border-radius-30`, `--kui-method-color-background-get` | CSS custom properties, SCSS/LESS variables, JS constants |
-| **Component** | `tokens/components/**` | `--kui-button-border-radius-medium`, `--kui-button-color-background-primary`, `--kui-button-shadow-focus` | Included in `KUI_THEMEABLE_TOKENS` — **no CSS value** |
-
-> **Alias tokens** (`tokens/alias/**`) form a third internal directory. They hold the raw palette values (hex colors, base sizes) that semantic tokens reference. They are **never exported** — they exist only so Style Dictionary can resolve `{color.alias.blue.100}` references at build time.
-
-### Semantic tokens
-
-Everything in `tokens/source/` is a semantic token — it has a concrete value and is exported to all formats (CSS, SCSS, LESS, JS). This includes:
-
-- **Scale tokens** — `--kui-color-*`, `--kui-space-*`, `--kui-border-radius-*`, `--kui-shadow-*`, `--kui-font-*`, etc. Named after the design dimension they represent.
-- **Domain tokens** (`tokens/source/domain/`) — `--kui-method-*`, `--kui-status-*`, `--kui-navigation-*`, `--kui-icon-*`. Named after a cross-cutting UI concept (HTTP methods, status codes, navigation chrome). Valued and exported exactly like scale tokens. **These are not component tokens** even though they're used inside components.
-
-### Component tokens — names only, value-less
-
-Component tokens (`--kui-button-*`, `--kui-card-*`, `--kui-input-*`, `--kui-badge-*`, …) live in `tokens/components/` and are **declared without any CSS value** — they are purely override slots. Every Kongponents component uses them in a `var()` fallback chain:
-
-```scss
-border-radius: var(--kui-button-border-radius-medium, var(--kui-border-radius-30, $kui-border-radius-30));
-//                 ↑ component token (empty by default)   ↑ semantic fallback        ↑ SCSS literal
-```
-
-When a theme writes `--kui-button-border-radius-medium: 999px`, only buttons go pill-shaped. Inputs and other components keep their semantic default. When no theme writes the token, `var()` falls through to the semantic default — **byte-identical to the un-themed render**.
-
-### Themeable token list
-
-The `./themeable-tokens` subpath exports `KUI_THEMEABLE_TOKENS` — a typed `readonly` tuple of every `--kui-*` custom property name that a theme may meaningfully override. It combines both semantic tokens and value-less component tokens.
-
-```ts
-import { KUI_THEMEABLE_TOKENS } from '@kong/design-tokens/themeable-tokens'
-
-// Derive a union type of all valid theme keys:
-type ThemeToken = typeof KUI_THEMEABLE_TOKENS[number]
-```
-
-**Breakpoint tokens are intentionally excluded.** `--kui-breakpoint-*` tokens are available as CSS custom properties and SCSS variables, but they cannot be consumed inside CSS `@media` feature queries — that is, `@media (min-width: var(--kui-breakpoint-md))` is invalid CSS. Kongponents uses breakpoints exclusively in `@media` rules, so overriding them via a theme has no effect on responsive behavior. Set breakpoints at the SCSS level instead if your project needs custom breakpoint values.
-
-## Themes
-
-Pre-built theme CSS files activate a complete set of token overrides via a `data-kui-theme` attribute on any element. Load a theme CSS file and then set the attribute on the root element (or any subtree element):
-
-```html
-<!-- In your HTML template or equivalent -->
-<html data-kui-theme="konnect-light">
-```
-
-```ts
-// Load the theme CSS — webpack/Vite will bundle it
-import '@kong/design-tokens/themes/konnect-light.css'
-
-// Switch the active theme at runtime
-document.documentElement.setAttribute('data-kui-theme', 'konnect-dark')
-```
-
-Available themes: `konnect-light`, `konnect-dark`, `brand-a`, `brand-b`.
-
-Each theme CSS file uses `@layer kui.theme { [data-kui-theme="name"] { ... } }`. This means customer `:root {}` overrides (which are **unlayered**) beat the theme automatically — no `!important` or special selectors needed.
-
-To respond to the system dark-mode preference, listen to the `prefers-color-scheme` media query in JS:
-
-```ts
-const mq = window.matchMedia('(prefers-color-scheme: dark)')
-const applyColorScheme = (dark: boolean) =>
-  document.documentElement.setAttribute('data-kui-theme', dark ? 'konnect-dark' : 'konnect-light')
-
-applyColorScheme(mq.matches)
-mq.addEventListener('change', e => applyColorScheme(e.matches))
-```
-
-You can also import the theme objects as JavaScript for runtime composition or for use with Kongponents' `applyTheme` / `defineKongponentsTheme`:
-
-```ts
-import { konnectDay, konnectNight, brandA, brandB } from '@kong/design-tokens/themes'
-```
-
 ## Tokens
 
+All design tokens **must** be placed inside of the `packages/design-tokens/tokens/` directory in one of two sub-directories.
+
 [View the lists of available tokens here](TOKENS.md), or keep reading for more information.
 
 ### Token Formats
@@ -336,55 +249,6 @@ Typically, a host application should only utilize the SCSS and/or JavaScript var
 </style>
 ```
 
-#### Kongponents
-
-[Kongponents](https://kongponents.konghq.com) ships its own `defineKongponentsTheme` helper that validates a theme object against the full typed token surface at authoring time. To use a pre-built design-tokens theme in Kongponents, wrap it with `defineKongponentsTheme`:
-
-```ts
-// my-app-theme.ts
-import { konnectDay } from '@kong/design-tokens/themes'
-import { defineKongponentsTheme } from '@kong/kongponents'
-
-export const myTheme = defineKongponentsTheme({
-  ...konnectDay,           // spread the base theme
-  '--kui-button-border-radius-medium': '999px',  // then override specific tokens
-})
-```
-
-Register the theme at app startup via the Kongponents plugin:
-
-```ts
-// main.ts
-import { createApp } from 'vue'
-import Kongponents from '@kong/kongponents'
-import { myTheme } from './my-app-theme'
-import App from './App.vue'
-
-createApp(App)
-  .use(Kongponents, { theme: myTheme })
-  .mount('#app')
-```
-
-Or apply a theme to a specific subtree at runtime using `KThemeProvider`:
-
-```vue
-<template>
-  <KThemeProvider :theme="myTheme">
-    <!-- everything here renders with myTheme active -->
-  </KThemeProvider>
-</template>
-```
-
-For per-tenant runtime composition (e.g. theme values fetched from an API), use `applyTheme` from `@kong/kongponents`:
-
-```ts
-import { applyTheme } from '@kong/kongponents'
-import { konnectDay } from '@kong/design-tokens/themes'
-
-// Merge the base theme with tenant-specific overrides, then apply to :root
-applyTheme({ ...konnectDay, ...tenantOverrides })
-```
-
 #### Server-Side Rendering (SSR)
 
 If your host application utilizes SSR, you may need to resolve aliases to the package exports.
@@ -412,26 +276,22 @@ To get started, install the package dependencies from the repo root:
 pnpm install
 ```
 
-### Directory structure
-
-The package is organized around four top-level source directories:
+### Token Requirements
 
-| Directory | Purpose |
-|-----------|---------|
-| `tokens/alias/` | **Internal alias palette** — raw CSS values (hex colors, base sizes) that semantic tokens reference via `{color.alias.*}`. Never exported in any build output; only used so Style Dictionary can resolve references at build time. |
-| `tokens/source/` | **Semantic tokens** — scale and domain tokens that are exported to `custom-properties.css`, SCSS, LESS, and JS. Subdirectories: `color/`, `space/`, `shadow/`, `font/`, `border/`, `animation/`, `breakpoint/`, `letter-spacing/`, `line-height/`, plus `domain/` for HTTP-method, status, navigation, and icon token families. |
-| `tokens/components/` | **Component tokens** — name-only override slots for Kongponents components (`button/`, `card/`, `input/`, `badge/`, …). All `$value` fields must be `""`. Included in `KUI_THEMEABLE_TOKENS` — no CSS, no SCSS/LESS/JS values emitted. |
-| `themes/` | **Named theme override sets** — each `{name}.json` lists the token values that activate for `[data-kui-theme="{name}"]`. Values may be raw hex or `{color.alias.*}` references resolved at build time. |
+- Tokens **must** be defined in the corresponding JSON files within the `packages/design-tokens/tokens/` directory in one of two sub-directories:
 
-### Token Requirements
+    Directory | Description
+    ---------|----------
+    `/tokens/alias` | The `alias` directory **must** only contain alias values that point directly to a raw CSS value. Any tokens defined within the `alias` directory **will not** be exposed in the package exports. Tokens defined in the `/tokens/alias/` directory can be utilized/referenced within the `/tokens/source/` files; however, these tokens will **NOT** be exported in the build files.
+    `/tokens/source` | The `source` directory contains all tokens that **will be** available for consumption from the package exports.
 
 - Token keys **must** be lowercase, snake_case, and defined in normal alphabetical order (rules enforced by the eslint config)
-- The `category` of each token should be its own directory (e.g. `tokens/source/color/`)
-- Each `type` of token should be a file in the `category` directory, named `{type}.json` (e.g. `tokens/source/color/background.json`)
-- If there is only a single `type` of token within a `category`, you **should** name the file `index.json` (e.g. `tokens/source/line-height/index.json`)
-- Alias tokens (`tokens/alias/`) **must not** be exposed/exported from the package exports
+- The `category` of each token should be its own directory (e.g. `tokens/color/`)
+- Each `type` of token should be a file in the `category` directory, named `{type}.json` (e.g. `tokens/color/background.json`)
+- If there is only a single `type` of token within a `category`, you **should** name the file `index.json` (e.g. `tokens/line-height/index.json`)
+- Component tokens **must** be defined within the `/tokens/source/components/` directory. All tokens for a component should be defined in a single JSON file, `{component-name}.json`, with the name of the component as the top-level property in the file.
+- Token aliases (e.g. color aliases) **must not** be exposed/exported from the package exports
 - Tokens at the "root" of their structure **must** be defined with a key of `"_"` to allow for nested child tokens.
-- Component tokens in `tokens/components/` **must always have `$value: ""`** — they are name-only slots with no CSS value. A non-empty `$value` is a build violation caught by the test suite.
 
     <details>
 
@@ -442,17 +302,17 @@ The package is organized around four top-level source directories:
       "color": {
         "text": {
           "_": {
-            "$description": "Default text color.",
-            "$value": "{color.alias.blue.100}"
+            "comment": "blue-100",
+            "value": "{color.alias.blue.100}"
           },
           "neutral": {
             "_": {
-              "$description": "Neutral text color.",
-              "$value": "{color.alias.gray.60}"
+              "comment": "gray-100",
+              "value": "{color.alias.gray.60}"
             },
             "strong": {
-              "$description": "Strong neutral text color.",
-              "$value": "{color.alias.gray.70}"
+              "comment": "gray-70",
+              "value": "{color.alias.gray.70}"
             }
           }
         }
@@ -469,50 +329,6 @@ The package is organized around four top-level source directories:
 
     </details>
 
-### Creating a new theme
-
-Use the `create-theme` script to scaffold a new theme file from the current `KUI_THEMEABLE_TOKENS` list. The script reads the built `dist/themeable-tokens.mjs` to get the canonical token list, and sources `$description` text from the actual token metadata.
-
-```sh
-# Scaffold an empty theme (all $value fields are "")
-pnpm create-theme my-brand
-
-# Start from a copy of an existing theme's values
-pnpm create-theme my-brand --from konnect-light
-```
-
-This creates `themes/my-brand.json`. The next build picks it up automatically — no code change is required.
-
-> **Prerequisites:** Run `pnpm build` at least once before running `create-theme` so `dist/themeable-tokens.mjs` exists.
-
-### Theme `$description` authoring rules
-
-Every token entry in a theme JSON file may carry an optional `$description` field. When present, it must follow these rules:
-
-- **Match the semantic token's description** — copy the text from the corresponding token in `tokens/source/`. Do not invent a different description for the same concept.
-- **Never reference a CSS value** — descriptions must be value-agnostic. The description explains *what* the token controls, not *what value* it currently holds.
-
-| ❌ Avoid | ✅ Use instead |
-|---|---|
-| `"2px border radius."` | _(omit — scale tokens are self-documenting by name)_ |
-| `"Background color for containers (white)."` | `"Default background color for containers."` |
-| `"Border color for danger actions or messages (red.60)."` | `"Border color for danger actions or messages."` |
-| `"0px 0px 0px 1px blue.60 inset"` | `"Primary state inset border shadow."` |
-
-**When to omit `$description` entirely:** pure scale tokens (`--kui-space-*`, `--kui-border-radius-0` through `-50`, `--kui-border-width-*`, `--kui-icon-size-*`, `--kui-line-height-*`, `--kui-letter-spacing-*`) are self-documenting — their token names carry all the meaning. Leave `$description` off these entries.
-
-**Component tokens may appear in theme files with `$description`.** A theme may set any component token (`--kui-button-*`, `--kui-card-*`, etc.) to provide per-component customization that diverges from the semantic fallback. Use the same description as the component token's source definition in `tokens/components/`.
-
-```json
-// ✅ Correct — description matches source definition
-"kui-button-border-radius-medium": {
-  "$description": "Medium button border radius.",
-  "$value": "999px"
-}
-```
-
-**A theme only needs to define tokens it overrides.** Omit any token whose value should remain at its semantic default (from `custom-properties.css`) or at whatever value a base theme already sets. The `[data-kui-theme]` CSS cascade handles the rest — unset tokens fall back through `var()` to the semantic layer automatically.
-
 ### Development Sandbox
 
 This package includes a Vue sandbox (see the `sandbox/` directory) to allow you to experiment with consuming tokens.
@@ -529,7 +345,7 @@ Or from within this package directory:
 pnpm sandbox
 ```
 
-This command simultaneously starts the Vite dev server and watches both the `tokens/` and `themes/` directories. Changes to either trigger a rebuild and restart the Vite dev server.
+This command will simultaneously start the Vite dev server and initialize a watcher on the `tokens/` directory. If any files in the `tokens/` directory are modified, the sandbox will automatically run the build command to update the tokens and then restart the Vite dev server (simulating hot module reload).
 
 Updating any files within the sandbox itself will also trigger hot module reload as expected.
 
@@ -583,7 +399,7 @@ For example, if I want to add a new `my-feature` folder, I'd update the `exports
 
 1. Ensure you are on the `main` branch, then pull down the latest code by running `git checkout main && git pull origin main`
 2. Checkout a new branch for your changes with `git checkout -b {type}/{jira-ticket}-{description}` — as an example, `git checkout feat/khcp-1234-add-color-tokens`
-3. Add/edit the tokens in the `tokens/` or `themes/` directory as needed, ensuring to adhere to the [Token Requirements](#token-requirements)
+3. Add/edit the tokens in the `packages/design-tokens/tokens/` directory as needed, ensuring to adhere to the [Token Requirements](#token-requirements)
 4. Before committing your changes, locally run `pnpm lint` to ensure you do not have any linting errors. If you have errors, you can try running `pnpm lint:fix` to resolve
 5. Commit your changes, adhering to [Conventional Commits](#committing-changes). To make this easier, you're encouraged to run `pnpm commit` from the repo root to help build your commit message
 6. Push your branch up to the remote with `git push origin {branch-name}`

package/dist/tokens/css/custom-properties.css

@@ -1,6 +1,6 @@
 /**
  * Do not edit directly, this file was auto-generated.
- * Generated on Tue, 23 Jun 2026 03:10:54 GMT
+ * Generated on Wed, 24 Jun 2026 12:57:36 GMT
  * 
  * Kong Konnect Design Tokens
  * GitHub: https://github.com/Kong/design-tokens/tree/main/packages/design-tokens

package/dist/tokens/js/cjs/index.d.ts

@@ -1,6 +1,6 @@
 /**
  * Do not edit directly, this file was auto-generated.
- * Generated on Tue, 23 Jun 2026 03:10:54 GMT
+ * Generated on Wed, 24 Jun 2026 12:57:36 GMT
  *
  * Kong Konnect Design Tokens
  * GitHub: https://github.com/Kong/design-tokens/tree/main/packages/design-tokens

package/dist/tokens/js/cjs/index.js

@@ -1,6 +1,6 @@
 /**
  * Do not edit directly, this file was auto-generated.
- * Generated on Tue, 23 Jun 2026 03:10:54 GMT
+ * Generated on Wed, 24 Jun 2026 12:57:36 GMT
  *
  * Kong Konnect Design Tokens
  * GitHub: https://github.com/Kong/design-tokens/tree/main/packages/design-tokens

package/dist/tokens/js/index.d.ts

@@ -1,6 +1,6 @@
 /**
  * Do not edit directly, this file was auto-generated.
- * Generated on Tue, 23 Jun 2026 03:10:54 GMT
+ * Generated on Wed, 24 Jun 2026 12:57:36 GMT
  *
  * Kong Konnect Design Tokens
  * GitHub: https://github.com/Kong/design-tokens/tree/main/packages/design-tokens

package/dist/tokens/js/index.mjs

@@ -1,6 +1,6 @@
 /**
  * Do not edit directly, this file was auto-generated.
- * Generated on Tue, 23 Jun 2026 03:10:54 GMT
+ * Generated on Wed, 24 Jun 2026 12:57:36 GMT
  *
  * Kong Konnect Design Tokens
  * GitHub: https://github.com/Kong/design-tokens/tree/main/packages/design-tokens

package/dist/tokens/less/variables.less

@@ -1,6 +1,6 @@
 
 // Do not edit directly, this file was auto-generated.
-// Generated on Tue, 23 Jun 2026 03:10:54 GMT
+// Generated on Wed, 24 Jun 2026 12:57:36 GMT
 // 
 // Kong Konnect Design Tokens
 // GitHub: https://github.com/Kong/design-tokens/tree/main/packages/design-tokens

package/dist/tokens/scss/_map.scss

@@ -1,7 +1,7 @@
 
 /**
  * Do not edit directly, this file was auto-generated.
- * Generated on Tue, 23 Jun 2026 03:10:54 GMT
+ * Generated on Wed, 24 Jun 2026 12:57:36 GMT
  * 
  * Kong Konnect Design Tokens
  * GitHub: https://github.com/Kong/design-tokens/tree/main/packages/design-tokens

package/dist/tokens/scss/_variables.scss

@@ -1,6 +1,6 @@
 
 // Do not edit directly, this file was auto-generated.
-// Generated on Tue, 23 Jun 2026 03:10:54 GMT
+// Generated on Wed, 24 Jun 2026 12:57:36 GMT
 // 
 // Kong Konnect Design Tokens
 // GitHub: https://github.com/Kong/design-tokens/tree/main/packages/design-tokens

package/package.json

@@ -1,9 +1,26 @@
 {
   "name": "@kong/design-tokens",
-  "version": "2.0.1-pr.670.ff5aeec.0",
+  "version": "2.0.1",
   "description": "Kong Konnect Design Tokens and style dictionary",
   "private": false,
   "type": "module",
+  "scripts": {
+    "build": "pnpm build:clean && pnpm build:tokens && pnpm copy:tokens-doc",
+    "build:tokens": "style-dictionary build --config ./config.mjs",
+    "build:clean": "rimraf ./dist",
+    "copy:tokens-doc": "shx cp -f './dist/tokens/README.md' './TOKENS.md'",
+    "lint": "eslint",
+    "lint:fix": "eslint --fix",
+    "typecheck": "pnpm typecheck:sandbox",
+    "typecheck:sandbox": "vue-tsc --project ./sandbox/tsconfig.json --noEmit",
+    "sandbox": "pnpm build && run-p sandbox:open sandbox:watch",
+    "sandbox:open": "vite sandbox -c ./sandbox/vite.config.ts",
+    "sandbox:watch": "chokidar \"tokens/**/*.json\" -c \"pnpm build\"",
+    "sandbox:build": "BUILD_SANDBOX=true vite build -c ./sandbox/vite.config.ts -m production",
+    "sandbox:preview": "BUILD_SANDBOX=true vite preview -c ./sandbox/vite.config.ts",
+    "watch:tokens": "pnpm build && chokidar \"tokens/**/*.json\" -c \"pnpm build\"",
+    "test": "vitest run --config vitest.config.mjs"
+  },
   "publishConfig": {
     "access": "public"
   },
@@ -25,37 +42,6 @@
         "default": "./dist/tokens/js/cjs/index.js"
       }
     },
-    "./themes": {
-      "import": {
-        "types": "./dist/themes/index.d.ts",
-        "default": "./dist/themes/index.mjs"
-      },
-      "require": {
-        "types": "./dist/themes/index.d.ts",
-        "default": "./dist/themes/index.mjs"
-      }
-    },
-    "./themes/*.css": "./dist/themes/*.css",
-    "./themes/*": {
-      "import": {
-        "types": "./dist/themes/*.d.ts",
-        "default": "./dist/themes/*.mjs"
-      },
-      "require": {
-        "types": "./dist/themes/*.d.ts",
-        "default": "./dist/themes/*.mjs"
-      }
-    },
-    "./themeable-tokens": {
-      "import": {
-        "types": "./dist/themeable-tokens.d.ts",
-        "default": "./dist/themeable-tokens.mjs"
-      },
-      "require": {
-        "types": "./dist/themeable-tokens.d.ts",
-        "default": "./dist/themeable-tokens.cjs"
-      }
-    },
     "./tokens/*": "./dist/tokens/*",
     "./package.json": "./package.json"
   },
@@ -70,7 +56,7 @@
     "url": "https://github.com/Kong/design-tokens/issues"
   },
   "devDependencies": {
-    "style-dictionary": "^5.4.0"
+    "style-dictionary": "^5.4.4"
   },
   "engines": {
     "node": ">=20.19.5",
@@ -79,24 +65,5 @@
   "volta": {
     "node": "24.13.1"
   },
-  "scripts": {
-    "build": "pnpm build:clean && pnpm build:tokens && pnpm copy:tokens-doc",
-    "build:tokens": "style-dictionary build --config ./config.mjs",
-    "build:clean": "rimraf ./dist",
-    "create-theme": "node scripts/create-theme.mjs",
-    "fill-themes": "node scripts/fill-themes.mjs",
-    "copy:tokens-doc": "shx cp -f './dist/tokens/README.md' './TOKENS.md'",
-    "lint": "eslint",
-    "lint:fix": "eslint --fix",
-    "typecheck": "pnpm typecheck:sandbox",
-    "typecheck:sandbox": "vue-tsc --project ./sandbox/tsconfig.json --noEmit",
-    "sandbox": "pnpm build && run-p sandbox:open sandbox:watch",
-    "sandbox:open": "vite sandbox -c ./sandbox/vite.config.ts",
-    "sandbox:watch": "chokidar \"tokens/**/*.json\" \"themes/**/*.json\" -c \"pnpm build\"",
-    "sandbox:build": "BUILD_SANDBOX=true vite build -c ./sandbox/vite.config.ts -m production",
-    "sandbox:preview": "BUILD_SANDBOX=true vite preview -c ./sandbox/vite.config.ts",
-    "watch:tokens": "pnpm build && chokidar \"tokens/**/*.json\" -c \"pnpm build\"",
-    "pretest": "pnpm build:tokens",
-    "test": "vitest run --config vitest.config.mjs"
-  }
-}
+  "gitHead": "be11746a643e282cc7319c46e9598340dad36c0a"
+}