@ox-content/vite-plugin 3.0.0-alpha.16 → 3.0.0-alpha.17

package/dist/theme-tokens2.d.cts

@@ -0,0 +1,75 @@
+//#region src/theme-tokens.d.ts
+/**
+ * Free-form `--octc-*` custom properties for themes that need more than the
+ * typed `colors` / `fonts` / `layout` fields.
+ *
+ * Keys are written **without** the `--octc-` prefix, so `"surface-glass"`
+ * becomes `--octc-surface-glass`. This is the seam that keeps the two theme
+ * axes independent: a color package can restyle code-block line markers, brand
+ * accents, and surface textures purely through tokens, while a skin package
+ * lays out geometry against those same tokens without knowing any color.
+ */
+type ThemeTokens = Record<string, string>;
+/**
+ * The token-bearing shape of a theme.
+ *
+ * Declared structurally instead of importing `ThemeConfig` so this module keeps
+ * an empty import graph: `@ox-content/vite-plugin/theme-tokens` has to be
+ * loadable by a bare (`ssg.bare: true`) or custom host that never pulls in the
+ * Vite plugin, the SSG, the native binding, or a filesystem API. Every
+ * `ThemeConfig` — including the published `@ox-content/theme-color-*` and
+ * `@ox-content/theme-*` packages — satisfies it.
+ */
+interface ThemeTokenSource {
+  tokens?: ThemeTokens;
+  darkTokens?: ThemeTokens;
+  extends?: ThemeTokenSource;
+}
+/**
+ * Options for {@link renderThemeTokenCss}.
+ */
+interface RenderThemeTokenCssOptions {
+  /**
+   * Keeps only the tokens whose name passes the predicate. Names arrive without
+   * the `--octc-` prefix, so `(name) => name.startsWith("syntax-")` reuses a
+   * color scheme's highlighter palette without adopting its page colors,
+   * typography, or layout policy.
+   *
+   * Filtering runs per layer, before merging, so a token a later layer would
+   * have overridden is dropped along with the override.
+   */
+  include?: (name: string) => boolean;
+}
+/**
+ * Renders a theme's `--octc-*` tokens as a standalone stylesheet.
+ *
+ * The built-in SSG emits these declarations itself, but `ssg.bare: true` and
+ * custom hosts render their own document — this is how they get the same
+ * tokens. The built-in highlighter emits `var(--octc-syntax-*)` references, so
+ * a bare host that wants only the highlighter palette can ask for it:
+ *
+ * ```ts
+ * import { renderThemeTokenCss } from "@ox-content/vite-plugin/theme-tokens";
+ * import { kanagawa } from "@ox-content/theme-color-kanagawa";
+ *
+ * const css = renderThemeTokenCss(kanagawa, {
+ *   include: (name) => name.startsWith("syntax-"),
+ * });
+ * ```
+ *
+ * Layers compose left to right and each layer's `extends` chain is flattened
+ * base-first, matching how `resolveTheme()` stacks a skin and a color scheme.
+ */
+declare function renderThemeTokenCss(theme: ThemeTokenSource | ThemeTokenSource[], options?: RenderThemeTokenCssOptions): string;
+/**
+ * Renders light and dark token records as the three selectors the SSG runtime
+ * switches between: an explicit `[data-theme="dark"]` opt-in, the OS
+ * `prefers-color-scheme` fallback, and the `:root` base.
+ *
+ * Emitted after the typed color variables and before the theme's own `css`, so
+ * a token can override a typed color and raw `css` can override a token.
+ */
+declare function tokensToCss(light: ThemeTokens, dark: ThemeTokens): string;
+//#endregion
+export { tokensToCss as a, renderThemeTokenCss as i, ThemeTokenSource as n, ThemeTokens as r, RenderThemeTokenCssOptions as t };
+//# sourceMappingURL=theme-tokens2.d.cts.map

package/dist/theme-tokens2.d.cts.map

@@ -0,0 +1 @@
+{"version":3,"file":"theme-tokens2.d.cts","names":[],"sources":["../src/theme-tokens.ts"],"mappings":";;;;;;;;;;;KAUY,cAAc;;;;;;;;;;;UAeT;EACf,SAAS;EACT,aAAa;EACb,UAAU;;;;;UAMK;;;;;;;;;;EAUf,WAAW;;;;;;;;;;;;;;;;;;;;;;iBAuBG,oBACd,OAAO,mBAAmB,oBAC1B,UAAS;;;;;;;;;iBAiBK,YAAY,OAAO,aAAa,MAAM"}

package/dist/theme-tokens2.d.mts

@@ -0,0 +1,75 @@
+//#region src/theme-tokens.d.ts
+/**
+ * Free-form `--octc-*` custom properties for themes that need more than the
+ * typed `colors` / `fonts` / `layout` fields.
+ *
+ * Keys are written **without** the `--octc-` prefix, so `"surface-glass"`
+ * becomes `--octc-surface-glass`. This is the seam that keeps the two theme
+ * axes independent: a color package can restyle code-block line markers, brand
+ * accents, and surface textures purely through tokens, while a skin package
+ * lays out geometry against those same tokens without knowing any color.
+ */
+type ThemeTokens = Record<string, string>;
+/**
+ * The token-bearing shape of a theme.
+ *
+ * Declared structurally instead of importing `ThemeConfig` so this module keeps
+ * an empty import graph: `@ox-content/vite-plugin/theme-tokens` has to be
+ * loadable by a bare (`ssg.bare: true`) or custom host that never pulls in the
+ * Vite plugin, the SSG, the native binding, or a filesystem API. Every
+ * `ThemeConfig` — including the published `@ox-content/theme-color-*` and
+ * `@ox-content/theme-*` packages — satisfies it.
+ */
+interface ThemeTokenSource {
+  tokens?: ThemeTokens;
+  darkTokens?: ThemeTokens;
+  extends?: ThemeTokenSource;
+}
+/**
+ * Options for {@link renderThemeTokenCss}.
+ */
+interface RenderThemeTokenCssOptions {
+  /**
+   * Keeps only the tokens whose name passes the predicate. Names arrive without
+   * the `--octc-` prefix, so `(name) => name.startsWith("syntax-")` reuses a
+   * color scheme's highlighter palette without adopting its page colors,
+   * typography, or layout policy.
+   *
+   * Filtering runs per layer, before merging, so a token a later layer would
+   * have overridden is dropped along with the override.
+   */
+  include?: (name: string) => boolean;
+}
+/**
+ * Renders a theme's `--octc-*` tokens as a standalone stylesheet.
+ *
+ * The built-in SSG emits these declarations itself, but `ssg.bare: true` and
+ * custom hosts render their own document — this is how they get the same
+ * tokens. The built-in highlighter emits `var(--octc-syntax-*)` references, so
+ * a bare host that wants only the highlighter palette can ask for it:
+ *
+ * ```ts
+ * import { renderThemeTokenCss } from "@ox-content/vite-plugin/theme-tokens";
+ * import { kanagawa } from "@ox-content/theme-color-kanagawa";
+ *
+ * const css = renderThemeTokenCss(kanagawa, {
+ *   include: (name) => name.startsWith("syntax-"),
+ * });
+ * ```
+ *
+ * Layers compose left to right and each layer's `extends` chain is flattened
+ * base-first, matching how `resolveTheme()` stacks a skin and a color scheme.
+ */
+declare function renderThemeTokenCss(theme: ThemeTokenSource | ThemeTokenSource[], options?: RenderThemeTokenCssOptions): string;
+/**
+ * Renders light and dark token records as the three selectors the SSG runtime
+ * switches between: an explicit `[data-theme="dark"]` opt-in, the OS
+ * `prefers-color-scheme` fallback, and the `:root` base.
+ *
+ * Emitted after the typed color variables and before the theme's own `css`, so
+ * a token can override a typed color and raw `css` can override a token.
+ */
+declare function tokensToCss(light: ThemeTokens, dark: ThemeTokens): string;
+//#endregion
+export { tokensToCss as a, renderThemeTokenCss as i, ThemeTokenSource as n, ThemeTokens as r, RenderThemeTokenCssOptions as t };
+//# sourceMappingURL=theme-tokens2.d.mts.map

package/dist/theme-tokens2.d.mts.map

@@ -0,0 +1 @@
+{"version":3,"file":"theme-tokens2.d.mts","names":[],"sources":["../src/theme-tokens.ts"],"mappings":";;;;;;;;;;;KAUY,cAAc;;;;;;;;;;;UAeT;EACf,SAAS;EACT,aAAa;EACb,UAAU;;;;;UAMK;;;;;;;;;;EAUf,WAAW;;;;;;;;;;;;;;;;;;;;;;iBAuBG,oBACd,OAAO,mBAAmB,oBAC1B,UAAS;;;;;;;;;iBAiBK,YAAY,OAAO,aAAa,MAAM"}

package/dist/vitepress.cjs

@@ -38,6 +38,7 @@ var __toESM = (mod, isNodeMode, target) => (target = mod != null ? __create(__ge
 }) : target, mod));
 var __toCommonJS = (mod) => __hasOwnProp.call(mod, "module.exports") ? mod["module.exports"] : __copyProps(__defProp({}, "__esModule", { value: true }), mod);
 //#endregion
+const require_napi = require("./napi.cjs");
 const require_theme_tokens = require("./theme-tokens.cjs");
 let node_module = require("node:module");
 let node_fs = require("node:fs");
@@ -45,36 +46,6 @@ let node_path = require("node:path");
 let node_crypto = require("node:crypto");
 let node_fs_promises = require("node:fs/promises");
 let glob = require("glob");
-//#region src/napi.ts
-const requireNapi = (0, node_module.createRequire)(require("url").pathToFileURL(__filename).href);
-function getDefaultExport(value) {
-	if (!value || typeof value !== "object" || !("default" in value)) return;
-	const defaultExport = value.default;
-	return defaultExport && typeof defaultExport === "object" ? defaultExport : void 0;
-}
-function normalizeNapiModule(mod) {
-	const defaultExport = getDefaultExport(mod);
-	return defaultExport ? {
-		...defaultExport,
-		...mod
-	} : mod;
-}
-async function importNapiModule() {
-	return normalizeNapiModule(await import("@ox-content/napi"));
-}
-let syncNapiModule;
-function importNapiModuleSync() {
-	if (syncNapiModule) return syncNapiModule;
-	if (syncNapiModule === null) throw new Error("[ox-content] @ox-content/napi is required. Please ensure the NAPI module is built.");
-	try {
-		syncNapiModule = normalizeNapiModule(requireNapi("@ox-content/napi"));
-		return syncNapiModule;
-	} catch {
-		syncNapiModule = null;
-		throw new Error("[ox-content] @ox-content/napi is required. Please ensure the NAPI module is built.");
-	}
-}
-//#endregion
 //#region src/theme-fonts-acquire.ts
 /**
 * Resolve self-hosted faces from a local file / `@fontsource` directory or
@@ -1245,7 +1216,7 @@ function formatObjectKey(key) {
 * Normalizes VitePress-specific frontmatter into ox-content's entry-page shape.
 */
 function normalizeVitePressFrontmatter(frontmatter) {
-	return importNapiModuleSync().normalizeVitePressFrontmatter(frontmatter);
+	return require_napi.importNapiModuleSync().normalizeVitePressFrontmatter(frontmatter);
 }
 //#endregion
 Object.defineProperty(exports, "__esmMin", {
@@ -1308,18 +1279,6 @@ Object.defineProperty(exports, "generateVitePressMigrationConfig", {
 		return generateVitePressMigrationConfig;
 	}
 });
-Object.defineProperty(exports, "importNapiModule", {
-	enumerable: true,
-	get: function() {
-		return importNapiModule;
-	}
-});
-Object.defineProperty(exports, "importNapiModuleSync", {
-	enumerable: true,
-	get: function() {
-		return importNapiModuleSync;
-	}
-});
 Object.defineProperty(exports, "mergeThemes", {
 	enumerable: true,
 	get: function() {