@mono-lit/helper 0.0.0-stage → 0.0.2

package/dist/src/vite/mono-client-only.d.ts

@@ -0,0 +1,35 @@
+import { Plugin } from 'vite';
+export interface MonoClientOnlyOptions {
+    prefix?: string;
+    wrapper?: string;
+    /**
+     * Tag names (e.g. `'mono-nav'`) to NOT wrap in the client-only wrapper.
+     * Use this for components that are server-rendered by another mechanism
+     * (e.g. `@lit-labs/ssr` / `nuxt-ssr-lit` shadow-DOM builds) — wrapping them
+     * in `<ClientOnly>` would suppress their server markup.
+     */
+    exclude?: string[];
+    /**
+     * Wrap LIGHT `<prefix*>` elements in the client-only wrapper. Default `true`.
+     * `false` leaves light tags untouched (they server-render as inert custom-element
+     * tags and upgrade in the browser) while the shadow `<LitWrapper>` wrap below
+     * keeps working — for apps whose pages are client-only as a whole and must not
+     * have each `<mono-*>` deferred past the page's `onMounted`.
+     */
+    lightWrap?: boolean;
+    /**
+     * Enable the import-driven SSR wrap: a `.vue` file that imports
+     * `@mono-lit/helper/ui/shadow/<entry>` gets its matching `<mono-*>` wrapped in
+     * `<LitWrapper>` (Declarative Shadow DOM) instead of `<ClientOnly>`. Needs
+     * `nuxt-ssr-lit` installed (provides the `<LitWrapper>` component). Default off.
+     */
+    litWrapper?: boolean;
+    /** Component name used for the SSR wrap. Default `'LitWrapper'`. */
+    litWrapperComponent?: string;
+    /**
+     * Tags to ALWAYS treat as shadow (LitWrapper-wrapped) regardless of per-file
+     * imports — for components registered once in a shared plugin. Default `[]`.
+     */
+    shadowOverride?: string[];
+}
+export declare function monoClientOnlyPlugin(options?: MonoClientOnlyOptions): Plugin;

package/dist/src/vite/mono-ssr-stub.d.ts

@@ -0,0 +1,20 @@
+import { Plugin } from 'vite';
+export interface MonoSsrStubOptions {
+    /**
+     * Import prefix whose side-effect (web component registration) modules
+     * should be stubbed during the server build. CSS entries are never stubbed.
+     */
+    packagePrefix?: string;
+}
+/**
+ * `@mono-lit/helper/ui/*` entries register Lit custom elements at module load
+ * (`class extends HTMLElement` + `customElements.define(...)`), which throws
+ * `HTMLElement is not defined` when evaluated in the Node SSR context.
+ *
+ * Every `<mono-*>` tag is already wrapped in `<ClientOnly>` and declared via
+ * `isCustomElement`, so nothing on the server needs these elements registered.
+ * This plugin resolves those side-effect imports to an empty module in the
+ * server build only — the client build keeps the real modules, so the elements
+ * still register and render after hydration.
+ */
+export declare function monoSsrStubPlugin(options?: MonoSsrStubOptions): Plugin;

package/dist/src/vite/shadow-manifest.d.ts

@@ -0,0 +1,8 @@
+export declare const SHADOW_ENTRY_TO_TAGS: Record<string, readonly string[]>;
+/** Flat list of every shadow-built custom-element tag. */
+export declare const SHADOW_TAGS: readonly string[];
+/**
+ * Extract the set of shadow tags a script block opts into, by scanning its
+ * `@mono-lit/helper/ui/shadow/<entry>` imports and mapping each entry to its tag(s).
+ */
+export declare function shadowTagsFromScript(script: string): Set<string>;