@ethisyscore/vite-plugin 1.59.0 → 1.62.0

package/dist/index.d.cts

@@ -312,8 +312,29 @@ interface PlatformReactPluginOptions {
  * (see `PlatformReactSurfaceMount.tsx` in `coreconnect-web`). This pass only
  * blocks remote/absolute paths at the manifest layer so a malformed manifest
  * fails fast.
+ *
+ * Returns an ARRAY: this pass plus the plugin-CSS scoping pass it must always be
+ * paired with. Vite flattens nested plugin arrays (`PluginOption` is recursively
+ * `PluginOption[]`), so existing call sites
+ * (`plugins: [react(), tailwindcss(), ethisysPlatformReactPlugin()]`) are unaffected.
+ *
+ * The pairing CANNOT be done by returning `{ plugins: [...] }` from this pass's own
+ * `config()` hook: Vite resolves the plugin container before running config hooks, so
+ * a plugin injected there is dropped SILENTLY (no warning, build still green) and the
+ * scoping pass would never run. Anything needing the page pass on its own as a single
+ * `Plugin` should call `ethisysPlatformReactPagesPlugin` and compose the scoping pass
+ * itself.
+ */
+declare function ethisysPlatformReactPlugin(options?: PlatformReactPluginOptions): Plugin[];
+/**
+ * The PlatformReact page-bundle pass ALONE, as a single `Plugin`.
+ *
+ * Prefer {@link ethisysPlatformReactPlugin}, which pairs this with the plugin-CSS
+ * scoping pass. Reach for this only when composing the passes by hand (a plugin with
+ * its own scoping step, or a test that drives one pass's hooks directly) — used on its
+ * own it emits UNSCOPED CSS, which leaks into the host document.
  */
-declare function ethisysPlatformReactPlugin(options?: PlatformReactPluginOptions): Plugin;
+declare function ethisysPlatformReactPagesPlugin(options?: PlatformReactPluginOptions): Plugin;
 
 /**
  * A fully-validated PlatformReact page declaration. All fields are guaranteed
@@ -534,6 +555,140 @@ declare function virtualPageEntry(page: PlatformReactPageInput, config: {
  */
 declare function buildPlatformReactPages(options?: BuildPlatformReactPagesOptions): Promise<PlatformReactBuildSummary>;
 
+/**
+ * Scope selector prefixed onto plugin-global CSS layers.
+ *
+ * `:where()` NOT `:is()` on purpose: `:where()` contributes ZERO specificity, so a
+ * scoped utility keeps exactly the specificity it had unscoped. Inside a plugin
+ * surface the cascade therefore behaves identically to before this transform; the
+ * only change is that the rule no longer matches host chrome. `:is()` would have
+ * raised every utility by one class and could flip a plugin's own conflicts.
+ *
+ * Two scope roots: the plugin root applied by `definePlatformReactPluginPage`, and
+ * the portal container marker, because MUI overlays render into a portal. Phase 1
+ * (`PluginPortalScope`) puts that container INSIDE the plugin root, so the second
+ * arm is redundant for SDK-managed overlays and exists for a plugin that supplies
+ * its own container element and marks it.
+ */
+declare const EHX_PLUGIN_CSS_SCOPE = ":where(.ehx-plugin-root, [data-ehx-plugin-portal])";
+/**
+ * Replacement for a document-root selector (`:root`, `:host`) in a plugin sheet.
+ *
+ * Tailwind's `theme` layer declares its scale as custom properties on
+ * `:root, :host` — `--spacing`, `--text-sm--line-height`, `--ease-*`,
+ * `--animate-*`. Injected into the host document that lands on the HOST root and
+ * silently redefines the host's own Tailwind scale for every element on the page:
+ * the same defect as the leaking utilities, one level deeper and inherited.
+ *
+ * These declarations cannot simply be dropped — the plugin's utilities read them —
+ * and prefixing is meaningless (`:where(.ehx-plugin-root) :root` matches nothing).
+ * They are REPLACED with the plugin root, which the whole surface inherits from.
+ *
+ * `:is()` here, not `:where()`: this is a substitution for a 0,1,0 selector, so
+ * matching that specificity is the faithful choice (a prefix is what must stay
+ * specificity-neutral). Note this only works because portal containment landed
+ * first — before that, overlays rendered outside the plugin root and would have
+ * lost the whole theme scale.
+ */
+declare const EHX_PLUGIN_ROOT_SCOPE = ":is(.ehx-plugin-root, [data-ehx-plugin-portal])";
+/**
+ * Cascade layers whose rules a plugin emits UNSCOPED and which therefore leak into
+ * the host document.
+ *
+ *   utilities  Tailwind's generated utility classes. The leak that motivated this:
+ *              a plugin's bare `.text-sm` is a duplicate of the host's own rule,
+ *              so it changes nothing until the host settles a specificity tie by
+ *              source order — then the plugin's copy, injected later, wins and
+ *              silently restyles host chrome.
+ *   properties Tailwind's `@property` fallback block, which sets ~40 `--tw-*`
+ *              custom properties on `*, :before, :after, ::backdrop` for the whole
+ *              document.
+ *
+ * The other layers are already scoped: `theme` holds custom properties on the
+ * plugin's own root class, and `base`/`components`/`mui` come from the SDK's
+ * `plugin-base.css`, which scopes everything to `.ehx-plugin-root`.
+ */
+declare const EHX_SCOPED_CSS_LAYERS: readonly string[];
+/**
+ * What counts as "scoped to a plugin" — the convention every plugin front-end
+ * adheres to, and the only thing the build guard needs to know.
+ *
+ *   .ehx-plugin-root           applied to every surface by the SDK page definer
+ *   .ethisys-<name>-root       the plugin's own root class (all plugins use this
+ *                              shape: ethisys-sales-root, ethisys-hr-root, …)
+ *   [data-ehx-plugin-portal]   the portal container overlays render into
+ *   :where(…) of the above     what {@link scopePluginCss} emits
+ *
+ * A selector that mentions NONE of these can match host chrome, which is the whole
+ * defect class. Matching anywhere in the selector (not just leftmost) is deliberate:
+ * `:where(.dark) .ethisys-sales-root` is scoped even though the root is not first.
+ */
+declare const EHX_PLUGIN_SCOPE_ROOTS: readonly RegExp[];
+interface ScopePluginCssOptions {
+    /** Descendant scope prefix. Default {@link EHX_PLUGIN_CSS_SCOPE}. */
+    scope?: string;
+    /** Replacement for `:root`/`:host`. Default {@link EHX_PLUGIN_ROOT_SCOPE}. */
+    rootScope?: string;
+    /** Layer names to scope. Default {@link EHX_SCOPED_CSS_LAYERS}. */
+    layers?: readonly string[];
+    /** What counts as scoped for the guard. Default {@link EHX_PLUGIN_SCOPE_ROOTS}. */
+    scopeRoots?: readonly RegExp[];
+    /**
+     * Guard behaviour when a selector would leak into the host document:
+     * `"error"` (default) fails the build, `"warn"` logs, `"off"` skips the check.
+     * Only reach for anything but `"error"` as a deliberate, time-boxed exception.
+     */
+    guard?: "error" | "warn" | "off";
+}
+/**
+ * Prefix every selector inside a plugin's UNSCOPED cascade layers with the plugin
+ * scope, so injecting the sheet into the host document cannot restyle host chrome.
+ *
+ * Pure and idempotent — running it twice is a no-op, so a rebuild or a second pass
+ * over already-scoped CSS is safe. See {@link EHX_SCOPED_CSS_LAYERS} for which
+ * layers are rewritten and why the others need no treatment.
+ */
+declare function scopePluginCss(css: string, options?: ScopePluginCssOptions): string;
+/**
+ * Every selector in `css` that mentions no plugin scope root, i.e. every selector
+ * that can reach host chrome once the sheet is injected into the host document.
+ *
+ * The invariant this checks is the whole convention: **a plugin never emits an
+ * unscoped selector.** {@link scopePluginCss} satisfies it automatically for the
+ * layers Tailwind generates; everything else is authored, and this is what catches
+ * an author (or a stray `@import "tailwindcss"` re-emitting global preflight) who
+ * did not. Pure, so a plugin's own build script or test can call it directly.
+ */
+declare function findUnscopedSelectors(css: string, options?: Pick<ScopePluginCssOptions, "scopeRoots">): string[];
+/** The build-failure message: what leaked, why it matters, and the usual cause. */
+declare function formatUnscopedSelectorError(id: string, leaks: readonly string[]): string;
+/** True for ids whose transform payload is plain CSS text we may rewrite. */
+declare function isScopableCssId(id: string): boolean;
+/**
+ * Vite plugin form of {@link scopePluginCss} PLUS the guard that makes it a
+ * convention rather than a courtesy, injected into every PlatformReact page
+ * sub-build by `buildPlatformReactPages`.
+ *
+ * Scoping Tailwind's generated layers is automatic; the guard fails the build if
+ * anything ELSE in the sheet is still unscoped (see
+ * {@link findUnscopedSelectors}). Together they are the enforceable form of one
+ * rule: a plugin never emits an unscoped selector into the host document. Prose in
+ * a standards doc did not hold across seven repos — the leak that prompted this
+ * shipped seven times, and the documented no-preflight rule was violated once
+ * without anyone noticing.
+ *
+ * Deliberately declares NO `enforce`. Vite resolves plugins in the order
+ * `[…prePlugins, vite:css, …normalPlugins, vite:css-post, …postPlugins]`, so a
+ * plugin with no `enforce` is the only position that sees compiled CSS:
+ *
+ *   - `@tailwindcss/vite` is `enforce: "pre"` and returns the generated sheet, so
+ *     the utilities exist by the time this runs.
+ *   - `vite:css-post` serialises a `*.css?inline` import into `export default "…"`.
+ *     `enforce: "post"` runs AFTER that and would be handed JavaScript, where the
+ *     CSS is an escaped string literal.
+ */
+declare function scopePluginCssPlugin(options?: ScopePluginCssOptions): Plugin;
+
 /**
  * Build-time codegen for a PlatformReact plugin's `feature.manifest.json` +
  * project-root `extension.manifest.json` overlay, from the plugin's `routeMeta.json`
@@ -807,4 +962,4 @@ interface EthisysPluginOptions {
  */
 declare function ethisysManifestPlugin(options?: EthisysPluginOptions): Plugin;
 
-export { type BuildPlatformReactPagesOptions, CONTRACT_B_IMPORT_MAP_ALLOWLIST, CONTRACT_B_RUNTIME_IMPORTS, CONTRACT_B_SEMANTIC_PRIMITIVES, type ComputePlatformReactPagesInput, type ComputePlatformReactPagesResult, type ContractAManifest, type ContractAPluginOptions, type ContractBManifest, type ContractBPluginOptions, type EthisysPluginOptions, type GeneratePlatformReactManifestConfig, type GeneratePlatformReactManifestResult, type IframeBuildContext, type IframeBuildOutputItem, type IframeBuildResult, type IframeSandboxBuildSummary, type IframeSandboxPluginOptions, type IframeViteBuild, type ManifestReactiveRuleRef, type ManifestResourceRef, PLATFORM_REACT_DEDUPE, PLATFORM_REACT_EXTERNALS, type ParsePlatformReactPagesOptions, type PlatformReactAlias, type PlatformReactBuildContext, type PlatformReactBuildSummary, type PlatformReactManifest, type PlatformReactManifestMeta, type PlatformReactManifestPaths, type PlatformReactPageDeclaration, type PlatformReactPageEntry, type PlatformReactPageInput, type PlatformReactPageOverride, type PlatformReactPageSource, type PlatformReactPluginOptions, type PlatformReactViteBuild, type ResolvedPlatformReactPage, type RouteMetaEntry, type ValidationFailure, type ValidationResult, type ViteBuildFn, buildIframeSandboxPages, buildPlatformReactPages, computePlatformReactPages, ethisysContractAPlugin, ethisysContractBPlugin, ethisysIframeSandboxPlugin, ethisysManifestPlugin, ethisysPlatformReactPlugin, generatePlatformReactManifest, parsePlatformReactPages, rewriteAliasedExternalImports, validateDeclarativeResource, validateReactiveRule, virtualPageEntry };
+export { type BuildPlatformReactPagesOptions, CONTRACT_B_IMPORT_MAP_ALLOWLIST, CONTRACT_B_RUNTIME_IMPORTS, CONTRACT_B_SEMANTIC_PRIMITIVES, type ComputePlatformReactPagesInput, type ComputePlatformReactPagesResult, type ContractAManifest, type ContractAPluginOptions, type ContractBManifest, type ContractBPluginOptions, EHX_PLUGIN_CSS_SCOPE, EHX_PLUGIN_ROOT_SCOPE, EHX_PLUGIN_SCOPE_ROOTS, EHX_SCOPED_CSS_LAYERS, type EthisysPluginOptions, type GeneratePlatformReactManifestConfig, type GeneratePlatformReactManifestResult, type IframeBuildContext, type IframeBuildOutputItem, type IframeBuildResult, type IframeSandboxBuildSummary, type IframeSandboxPluginOptions, type IframeViteBuild, type ManifestReactiveRuleRef, type ManifestResourceRef, PLATFORM_REACT_DEDUPE, PLATFORM_REACT_EXTERNALS, type ParsePlatformReactPagesOptions, type PlatformReactAlias, type PlatformReactBuildContext, type PlatformReactBuildSummary, type PlatformReactManifest, type PlatformReactManifestMeta, type PlatformReactManifestPaths, type PlatformReactPageDeclaration, type PlatformReactPageEntry, type PlatformReactPageInput, type PlatformReactPageOverride, type PlatformReactPageSource, type PlatformReactPluginOptions, type PlatformReactViteBuild, type ResolvedPlatformReactPage, type RouteMetaEntry, type ScopePluginCssOptions, type ValidationFailure, type ValidationResult, type ViteBuildFn, buildIframeSandboxPages, buildPlatformReactPages, computePlatformReactPages, ethisysContractAPlugin, ethisysContractBPlugin, ethisysIframeSandboxPlugin, ethisysManifestPlugin, ethisysPlatformReactPagesPlugin, ethisysPlatformReactPlugin, findUnscopedSelectors, formatUnscopedSelectorError, generatePlatformReactManifest, isScopableCssId, parsePlatformReactPages, rewriteAliasedExternalImports, scopePluginCss, scopePluginCssPlugin, validateDeclarativeResource, validateReactiveRule, virtualPageEntry };

package/dist/index.d.ts

@@ -312,8 +312,29 @@ interface PlatformReactPluginOptions {
  * (see `PlatformReactSurfaceMount.tsx` in `coreconnect-web`). This pass only
  * blocks remote/absolute paths at the manifest layer so a malformed manifest
  * fails fast.
+ *
+ * Returns an ARRAY: this pass plus the plugin-CSS scoping pass it must always be
+ * paired with. Vite flattens nested plugin arrays (`PluginOption` is recursively
+ * `PluginOption[]`), so existing call sites
+ * (`plugins: [react(), tailwindcss(), ethisysPlatformReactPlugin()]`) are unaffected.
+ *
+ * The pairing CANNOT be done by returning `{ plugins: [...] }` from this pass's own
+ * `config()` hook: Vite resolves the plugin container before running config hooks, so
+ * a plugin injected there is dropped SILENTLY (no warning, build still green) and the
+ * scoping pass would never run. Anything needing the page pass on its own as a single
+ * `Plugin` should call `ethisysPlatformReactPagesPlugin` and compose the scoping pass
+ * itself.
+ */
+declare function ethisysPlatformReactPlugin(options?: PlatformReactPluginOptions): Plugin[];
+/**
+ * The PlatformReact page-bundle pass ALONE, as a single `Plugin`.
+ *
+ * Prefer {@link ethisysPlatformReactPlugin}, which pairs this with the plugin-CSS
+ * scoping pass. Reach for this only when composing the passes by hand (a plugin with
+ * its own scoping step, or a test that drives one pass's hooks directly) — used on its
+ * own it emits UNSCOPED CSS, which leaks into the host document.
  */
-declare function ethisysPlatformReactPlugin(options?: PlatformReactPluginOptions): Plugin;
+declare function ethisysPlatformReactPagesPlugin(options?: PlatformReactPluginOptions): Plugin;
 
 /**
  * A fully-validated PlatformReact page declaration. All fields are guaranteed
@@ -534,6 +555,140 @@ declare function virtualPageEntry(page: PlatformReactPageInput, config: {
  */
 declare function buildPlatformReactPages(options?: BuildPlatformReactPagesOptions): Promise<PlatformReactBuildSummary>;
 
+/**
+ * Scope selector prefixed onto plugin-global CSS layers.
+ *
+ * `:where()` NOT `:is()` on purpose: `:where()` contributes ZERO specificity, so a
+ * scoped utility keeps exactly the specificity it had unscoped. Inside a plugin
+ * surface the cascade therefore behaves identically to before this transform; the
+ * only change is that the rule no longer matches host chrome. `:is()` would have
+ * raised every utility by one class and could flip a plugin's own conflicts.
+ *
+ * Two scope roots: the plugin root applied by `definePlatformReactPluginPage`, and
+ * the portal container marker, because MUI overlays render into a portal. Phase 1
+ * (`PluginPortalScope`) puts that container INSIDE the plugin root, so the second
+ * arm is redundant for SDK-managed overlays and exists for a plugin that supplies
+ * its own container element and marks it.
+ */
+declare const EHX_PLUGIN_CSS_SCOPE = ":where(.ehx-plugin-root, [data-ehx-plugin-portal])";
+/**
+ * Replacement for a document-root selector (`:root`, `:host`) in a plugin sheet.
+ *
+ * Tailwind's `theme` layer declares its scale as custom properties on
+ * `:root, :host` — `--spacing`, `--text-sm--line-height`, `--ease-*`,
+ * `--animate-*`. Injected into the host document that lands on the HOST root and
+ * silently redefines the host's own Tailwind scale for every element on the page:
+ * the same defect as the leaking utilities, one level deeper and inherited.
+ *
+ * These declarations cannot simply be dropped — the plugin's utilities read them —
+ * and prefixing is meaningless (`:where(.ehx-plugin-root) :root` matches nothing).
+ * They are REPLACED with the plugin root, which the whole surface inherits from.
+ *
+ * `:is()` here, not `:where()`: this is a substitution for a 0,1,0 selector, so
+ * matching that specificity is the faithful choice (a prefix is what must stay
+ * specificity-neutral). Note this only works because portal containment landed
+ * first — before that, overlays rendered outside the plugin root and would have
+ * lost the whole theme scale.
+ */
+declare const EHX_PLUGIN_ROOT_SCOPE = ":is(.ehx-plugin-root, [data-ehx-plugin-portal])";
+/**
+ * Cascade layers whose rules a plugin emits UNSCOPED and which therefore leak into
+ * the host document.
+ *
+ *   utilities  Tailwind's generated utility classes. The leak that motivated this:
+ *              a plugin's bare `.text-sm` is a duplicate of the host's own rule,
+ *              so it changes nothing until the host settles a specificity tie by
+ *              source order — then the plugin's copy, injected later, wins and
+ *              silently restyles host chrome.
+ *   properties Tailwind's `@property` fallback block, which sets ~40 `--tw-*`
+ *              custom properties on `*, :before, :after, ::backdrop` for the whole
+ *              document.
+ *
+ * The other layers are already scoped: `theme` holds custom properties on the
+ * plugin's own root class, and `base`/`components`/`mui` come from the SDK's
+ * `plugin-base.css`, which scopes everything to `.ehx-plugin-root`.
+ */
+declare const EHX_SCOPED_CSS_LAYERS: readonly string[];
+/**
+ * What counts as "scoped to a plugin" — the convention every plugin front-end
+ * adheres to, and the only thing the build guard needs to know.
+ *
+ *   .ehx-plugin-root           applied to every surface by the SDK page definer
+ *   .ethisys-<name>-root       the plugin's own root class (all plugins use this
+ *                              shape: ethisys-sales-root, ethisys-hr-root, …)
+ *   [data-ehx-plugin-portal]   the portal container overlays render into
+ *   :where(…) of the above     what {@link scopePluginCss} emits
+ *
+ * A selector that mentions NONE of these can match host chrome, which is the whole
+ * defect class. Matching anywhere in the selector (not just leftmost) is deliberate:
+ * `:where(.dark) .ethisys-sales-root` is scoped even though the root is not first.
+ */
+declare const EHX_PLUGIN_SCOPE_ROOTS: readonly RegExp[];
+interface ScopePluginCssOptions {
+    /** Descendant scope prefix. Default {@link EHX_PLUGIN_CSS_SCOPE}. */
+    scope?: string;
+    /** Replacement for `:root`/`:host`. Default {@link EHX_PLUGIN_ROOT_SCOPE}. */
+    rootScope?: string;
+    /** Layer names to scope. Default {@link EHX_SCOPED_CSS_LAYERS}. */
+    layers?: readonly string[];
+    /** What counts as scoped for the guard. Default {@link EHX_PLUGIN_SCOPE_ROOTS}. */
+    scopeRoots?: readonly RegExp[];
+    /**
+     * Guard behaviour when a selector would leak into the host document:
+     * `"error"` (default) fails the build, `"warn"` logs, `"off"` skips the check.
+     * Only reach for anything but `"error"` as a deliberate, time-boxed exception.
+     */
+    guard?: "error" | "warn" | "off";
+}
+/**
+ * Prefix every selector inside a plugin's UNSCOPED cascade layers with the plugin
+ * scope, so injecting the sheet into the host document cannot restyle host chrome.
+ *
+ * Pure and idempotent — running it twice is a no-op, so a rebuild or a second pass
+ * over already-scoped CSS is safe. See {@link EHX_SCOPED_CSS_LAYERS} for which
+ * layers are rewritten and why the others need no treatment.
+ */
+declare function scopePluginCss(css: string, options?: ScopePluginCssOptions): string;
+/**
+ * Every selector in `css` that mentions no plugin scope root, i.e. every selector
+ * that can reach host chrome once the sheet is injected into the host document.
+ *
+ * The invariant this checks is the whole convention: **a plugin never emits an
+ * unscoped selector.** {@link scopePluginCss} satisfies it automatically for the
+ * layers Tailwind generates; everything else is authored, and this is what catches
+ * an author (or a stray `@import "tailwindcss"` re-emitting global preflight) who
+ * did not. Pure, so a plugin's own build script or test can call it directly.
+ */
+declare function findUnscopedSelectors(css: string, options?: Pick<ScopePluginCssOptions, "scopeRoots">): string[];
+/** The build-failure message: what leaked, why it matters, and the usual cause. */
+declare function formatUnscopedSelectorError(id: string, leaks: readonly string[]): string;
+/** True for ids whose transform payload is plain CSS text we may rewrite. */
+declare function isScopableCssId(id: string): boolean;
+/**
+ * Vite plugin form of {@link scopePluginCss} PLUS the guard that makes it a
+ * convention rather than a courtesy, injected into every PlatformReact page
+ * sub-build by `buildPlatformReactPages`.
+ *
+ * Scoping Tailwind's generated layers is automatic; the guard fails the build if
+ * anything ELSE in the sheet is still unscoped (see
+ * {@link findUnscopedSelectors}). Together they are the enforceable form of one
+ * rule: a plugin never emits an unscoped selector into the host document. Prose in
+ * a standards doc did not hold across seven repos — the leak that prompted this
+ * shipped seven times, and the documented no-preflight rule was violated once
+ * without anyone noticing.
+ *
+ * Deliberately declares NO `enforce`. Vite resolves plugins in the order
+ * `[…prePlugins, vite:css, …normalPlugins, vite:css-post, …postPlugins]`, so a
+ * plugin with no `enforce` is the only position that sees compiled CSS:
+ *
+ *   - `@tailwindcss/vite` is `enforce: "pre"` and returns the generated sheet, so
+ *     the utilities exist by the time this runs.
+ *   - `vite:css-post` serialises a `*.css?inline` import into `export default "…"`.
+ *     `enforce: "post"` runs AFTER that and would be handed JavaScript, where the
+ *     CSS is an escaped string literal.
+ */
+declare function scopePluginCssPlugin(options?: ScopePluginCssOptions): Plugin;
+
 /**
  * Build-time codegen for a PlatformReact plugin's `feature.manifest.json` +
  * project-root `extension.manifest.json` overlay, from the plugin's `routeMeta.json`
@@ -807,4 +962,4 @@ interface EthisysPluginOptions {
  */
 declare function ethisysManifestPlugin(options?: EthisysPluginOptions): Plugin;
 
-export { type BuildPlatformReactPagesOptions, CONTRACT_B_IMPORT_MAP_ALLOWLIST, CONTRACT_B_RUNTIME_IMPORTS, CONTRACT_B_SEMANTIC_PRIMITIVES, type ComputePlatformReactPagesInput, type ComputePlatformReactPagesResult, type ContractAManifest, type ContractAPluginOptions, type ContractBManifest, type ContractBPluginOptions, type EthisysPluginOptions, type GeneratePlatformReactManifestConfig, type GeneratePlatformReactManifestResult, type IframeBuildContext, type IframeBuildOutputItem, type IframeBuildResult, type IframeSandboxBuildSummary, type IframeSandboxPluginOptions, type IframeViteBuild, type ManifestReactiveRuleRef, type ManifestResourceRef, PLATFORM_REACT_DEDUPE, PLATFORM_REACT_EXTERNALS, type ParsePlatformReactPagesOptions, type PlatformReactAlias, type PlatformReactBuildContext, type PlatformReactBuildSummary, type PlatformReactManifest, type PlatformReactManifestMeta, type PlatformReactManifestPaths, type PlatformReactPageDeclaration, type PlatformReactPageEntry, type PlatformReactPageInput, type PlatformReactPageOverride, type PlatformReactPageSource, type PlatformReactPluginOptions, type PlatformReactViteBuild, type ResolvedPlatformReactPage, type RouteMetaEntry, type ValidationFailure, type ValidationResult, type ViteBuildFn, buildIframeSandboxPages, buildPlatformReactPages, computePlatformReactPages, ethisysContractAPlugin, ethisysContractBPlugin, ethisysIframeSandboxPlugin, ethisysManifestPlugin, ethisysPlatformReactPlugin, generatePlatformReactManifest, parsePlatformReactPages, rewriteAliasedExternalImports, validateDeclarativeResource, validateReactiveRule, virtualPageEntry };
+export { type BuildPlatformReactPagesOptions, CONTRACT_B_IMPORT_MAP_ALLOWLIST, CONTRACT_B_RUNTIME_IMPORTS, CONTRACT_B_SEMANTIC_PRIMITIVES, type ComputePlatformReactPagesInput, type ComputePlatformReactPagesResult, type ContractAManifest, type ContractAPluginOptions, type ContractBManifest, type ContractBPluginOptions, EHX_PLUGIN_CSS_SCOPE, EHX_PLUGIN_ROOT_SCOPE, EHX_PLUGIN_SCOPE_ROOTS, EHX_SCOPED_CSS_LAYERS, type EthisysPluginOptions, type GeneratePlatformReactManifestConfig, type GeneratePlatformReactManifestResult, type IframeBuildContext, type IframeBuildOutputItem, type IframeBuildResult, type IframeSandboxBuildSummary, type IframeSandboxPluginOptions, type IframeViteBuild, type ManifestReactiveRuleRef, type ManifestResourceRef, PLATFORM_REACT_DEDUPE, PLATFORM_REACT_EXTERNALS, type ParsePlatformReactPagesOptions, type PlatformReactAlias, type PlatformReactBuildContext, type PlatformReactBuildSummary, type PlatformReactManifest, type PlatformReactManifestMeta, type PlatformReactManifestPaths, type PlatformReactPageDeclaration, type PlatformReactPageEntry, type PlatformReactPageInput, type PlatformReactPageOverride, type PlatformReactPageSource, type PlatformReactPluginOptions, type PlatformReactViteBuild, type ResolvedPlatformReactPage, type RouteMetaEntry, type ScopePluginCssOptions, type ValidationFailure, type ValidationResult, type ViteBuildFn, buildIframeSandboxPages, buildPlatformReactPages, computePlatformReactPages, ethisysContractAPlugin, ethisysContractBPlugin, ethisysIframeSandboxPlugin, ethisysManifestPlugin, ethisysPlatformReactPagesPlugin, ethisysPlatformReactPlugin, findUnscopedSelectors, formatUnscopedSelectorError, generatePlatformReactManifest, isScopableCssId, parsePlatformReactPages, rewriteAliasedExternalImports, scopePluginCss, scopePluginCssPlugin, validateDeclarativeResource, validateReactiveRule, virtualPageEntry };