@appshell/webpack-plugin 1.0.0-alpha.25 → 1.0.0-alpha.27

package/dist/types/tokens/src/index.d.ts

@@ -1,4 +1,4 @@
 export * from './contract';
 export { contrastRatio, describeFinding, parseColor, toHex, validateTheme, type ContrastFinding, } from './contrast';
 export { ACCENTS, BASES, FOCUS_RINGS } from './presets';
-export { composeTheme, DEFAULT_TYPE_AND_DIMENSIONS, pinnedMode, toCss, type ColorScheme, type ThemeSelection, } from './theme';
+export { DEFAULT_TYPE_AND_DIMENSIONS, composeTheme, cssFrom, pinnedMode, resolveTheme, toCss, type ColorScheme, type CssOptions, type ResolvedTheme, type ThemeSelection, } from './theme';

package/dist/types/tokens/src/theme.d.ts

@@ -22,9 +22,33 @@ export declare const pinnedMode: (selection: ThemeSelection) => Mode | undefined
 export declare const DEFAULT_TYPE_AND_DIMENSIONS: Record<string, string>;
 /** The full token map for one mode. */
 export declare const composeTheme: (selection: ThemeSelection, mode: Mode) => Theme;
+/**
+ * A theme with both modes already worked out.
+ *
+ * This is the shape a *published* theme stores. Resolving a selection and emitting CSS
+ * used to be one step, which meant the only way to render a theme was to re-resolve its
+ * preset names — so the values behind a name lived in whatever build was deployed, and an
+ * Application's recorded appearance moved when that build did. Materialising both modes
+ * lets the values be stored, versioned and rendered from, rather than looked up.
+ */
+export type ResolvedTheme = Record<Mode, Theme>;
+/** Works out both modes of a selection, including any overrides it carries. */
+export declare const resolveTheme: (selection: ThemeSelection) => ResolvedTheme;
+export type CssOptions = {
+    /** Defaults to `system`. Belongs to whoever is rendering, not to the theme. */
+    colorScheme?: ColorScheme;
+    /** Applied over the resolved values, so a consumer can adjust without forking. */
+    overrides?: Partial<Theme>;
+};
 /**
  * Three states, not two: an explicit choice in either direction, and the system default
  * when nothing is stamped on the root. A theme that only handled `prefers-color-scheme`
  * would give a viewer no way to override it.
  */
+export declare const cssFrom: (resolved: ResolvedTheme, options?: CssOptions) => string;
+/**
+ * Resolve and emit in one step. The authoring path — a preset name in hand, CSS wanted.
+ * The registry uses `cssFrom` against a stored theme instead, so what it renders cannot
+ * drift from what was published.
+ */
 export declare const toCss: (selection: ThemeSelection) => string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@appshell/webpack-plugin",
-  "version": "1.0.0-alpha.25",
+  "version": "1.0.0-alpha.27",
   "description": "Webpack plugin used to generate a global Appshell configuration for micro-frontends built with Module Federation",
   "main": "dist/main.js",
   "types": "dist/types/webpack-plugin/src/index.d.ts",
@@ -32,8 +32,8 @@
     "plugin"
   ],
   "license": "MIT",
-  "gitHead": "7d90eb91be3cb50aae5aaa680063878dfcaafea2",
+  "gitHead": "425a1894db52f7b8da1a3c10ea9fca7f6e48a13c",
   "dependencies": {
-    "@appshell/tokens": "^1.0.0-alpha.25"
+    "@appshell/tokens": "^1.0.0-alpha.27"
   }
 }