@fusion.dev/helix-theme 0.0.10 → 0.3.0

package/dist/index.js

@@ -1,38 +1,5 @@
-/**
- * The theme engine, reached from JavaScript.
- *
- * **One implementation, two distributions.** The derivation is Rust: it is a
- * search, and `fitToGamut` is a twenty-step bisection while
- * `lightnessForContrast` searches too, so iteration count, bisection order and
- * float arithmetic are implementation choices. Two implementations of that
- * disagree by construction rather than by accident, which is why this package
- * stopped being an engine and became a way to reach one.
- *
- * **It has to be awaited, and there is no way around that.** WebAssembly
- * instantiates asynchronously, so a module-level `deriveTheme` would either
- * block or throw for anybody who called it before the module landed. Handing the
- * engine back from `initTheme` makes the fact unavoidable rather than a runtime
- * error somebody meets in production: you cannot hold a `ThemeEngine` without
- * having waited for one.
- *
- * ```ts
- * const engine = await initTheme('/helix/theme.wasm')
- * const theme = engine.derive({ brand: '#3b82f6' }, [':root'])
- * document.head.append(Object.assign(document.createElement('style'), {
- *   textContent: theme.css[':root'],
- * }))
- * ```
- */
 import initWasm, { derive, hexToOklch as readHex } from '../wasm/fusion_helix_theme.js';
 let loading;
-/**
- * Loads the engine, once.
- *
- * **The promise is cached rather than the result**, so two callers racing at
- * startup get one instantiation and both wait on it. Caching the resolved value
- * instead would let the second call start a second download before the first
- * finished.
- */
 export function initTheme(source) {
     loading ??= initWasm({ module_or_path: source }).then(() => ({
         derive: (intent, selectors = []) => JSON.parse(derive(JSON.stringify(intent), JSON.stringify(selectors))),

package/dist/types.js

@@ -1,10 +1 @@
-/**
- * The shapes a consumer writes and the shapes they get back.
- *
- * **Declarations only.** The derivation is Rust, reached through WebAssembly, so
- * what a JavaScript consumer needs from this package is the vocabulary rather
- * than the solver. A type is erased at build time, so nothing here is a second
- * implementation of anything: it cannot drift into disagreeing with the engine
- * about an *answer*, only about a *field name*, which is what is compared.
- */
 export {};

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fusion.dev/helix-theme",
   "description": "Theme derivation engine. Computes a complete, contrast-guaranteed token set from intent inputs.",
-  "version": "0.0.10",
+  "version": "0.3.0",
   "license": "MIT",
   "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
   "repository": {
@@ -24,7 +24,7 @@
   ],
   "sideEffects": false,
   "scripts": {
-    "build": "tsc -p tsconfig.json",
+    "build": "tsc -p tsconfig.json && tsc -p tsconfig.types.json",
     "test": "cargo test -p fusion-helix-theme --manifest-path ../../Cargo.toml",
     "typecheck": "tsc -p tsconfig.json --noEmit",
     "wasm": "node scripts/build-wasm.mjs",