@qwik-custom-elements/adapter-stencil 1.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Dmitry A. Efimenko
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,420 @@
+# @qwik-custom-elements/adapter-stencil
+
+Qwik runtime helpers for integrating Stencil custom elements.
+
+## Install
+
+```
+npm install @qwik-custom-elements/adapter-stencil
+```
+
+Peer dependencies:
+
+```
+npm install @builder.io/qwik @builder.io/qwik-city @stencil/core
+```
+
+## Quickstart
+
+Reference this adapter in your `qwik-custom-elements.config.json`:
+
+```json
+{
+  "projects": [
+    {
+      "id": "my-stencil-lib",
+      "adapter": "stencil",
+      "adapterPackage": "@qwik-custom-elements/adapter-stencil",
+      "source": {
+        "type": "PACKAGE_NAME",
+        "packageName": "my-stencil-lib"
+      },
+      "adapterOptions": {
+        "runtime": {
+          "loaderImport": "my-stencil-lib/loader",
+          "hydrateImport": "my-stencil-lib/hydrate"
+        }
+      },
+      "outDir": "./src/generated/stencil/ssr"
+    }
+  ]
+}
+```
+
+Omit `hydrateImport` to generate a CSR-only (loader-only) surface without Stencil SSR.
+
+Run `npx qwik-custom-elements` to generate Qwik wrappers from the Stencil component library.
+
+See the [Manual Runtime Usage](#manual-runtime-usage) section below for direct API usage without the generator.
+
+## Support Policy
+
+This package follows semantic versioning. See [COMPATIBILITY.md](../../COMPATIBILITY.md) for tested combinations of adapter-stencil, Qwik, Stencil, and Node.js.
+
+Breaking changes always include an explicit `BREAKING` section in the release notes and require an update to `COMPATIBILITY.md` before merging.
+
+## Ownership Boundary
+
+`@qwik-custom-elements/adapter-stencil` owns Stencil-specific generation behavior and runtime integration.
+
+That ownership includes:
+
+- Stencil capability metadata
+- Stencil runtime import resolution and validation
+- Stencil SSR probing and SSR bridge behavior
+- adapter-owned generated barrels, runtime helper modules, wrapper modules, and file extensions
+- framework-specific output shape decisions that must not live in core
+
+Core may orchestrate the run and pass typed parsed component metadata into this adapter, but core should not branch on adapter identity to shape Stencil-generated output directly.
+
+## Current Exports
+
+This package exposes two runtime entrypoints:
+
+- `@qwik-custom-elements/adapter-stencil/client`
+  - `createStencilClientSetup(...)`
+  - `createStencilCSRComponent()`
+- `@qwik-custom-elements/adapter-stencil/ssr`
+  - `createStencilSSRComponent(...)`
+  - SSR model and style helpers
+
+These APIs let an app or generated wrapper layer bootstrap Stencil custom elements on the client and render them through a Qwik SSR bridge when hydrate-backed SSR is available.
+
+`createStencilCSRComponent` provides the client-only rendering bridge for loader-only generation. It renders the custom element tag directly, wires events on the client, projects slots, and does not depend on Stencil server rendering.
+
+## Manual Runtime Usage
+
+```tsx
+import { $ } from '@builder.io/qwik';
+import { createStencilClientSetup } from '@qwik-custom-elements/adapter-stencil/client';
+import {
+  createStencilSSRComponent,
+  type StencilRenderToString,
+} from '@qwik-custom-elements/adapter-stencil/ssr';
+
+import { defineCustomElements } from '@acme/stencil-lib/loader';
+
+const renderToString: StencilRenderToString = async (input, options) => {
+  const hydrateModuleId = '@acme/stencil-lib/hydrate';
+  const { renderToString } = await import(/* @vite-ignore */ hydrateModuleId);
+  return renderToString(input, options);
+};
+
+export const useAcmeClientSetup = createStencilClientSetup(
+  $(async () => {
+    await Promise.resolve(defineCustomElements());
+  }),
+);
+
+export const AcmeStencilComponent = createStencilSSRComponent(
+  $(renderToString),
+);
+```
+
+## Source Types For Generation
+
+The generator contract supports two source types for Stencil projects:
+
+- `PACKAGE_NAME`
+- `CEM`
+
+The intended direction is that both source types can generate the same consumer-facing output shape when enough runtime information is available:
+
+- a shared Stencil bridge/runtime module
+- individual typed Qwik wrappers for each Stencil component
+
+The difference between the two source types is input contract and discovery model, not desired output.
+
+## `PACKAGE_NAME`
+
+Use `PACKAGE_NAME` when the Stencil library is consumable as a package and you want package-aware discovery.
+
+Example config:
+
+```json
+{
+  "projects": [
+    {
+      "id": "demo",
+      "adapter": "stencil",
+      "adapterPackage": "@qwik-custom-elements/adapter-stencil",
+      "source": {
+        "type": "PACKAGE_NAME",
+        "packageName": "@acme/stencil-lib"
+      },
+      "outDir": "./apps/qwik-demo/src/generated/acme",
+      "cleanOutput": true,
+      "adapterOptions": {
+        "runtime": {
+          "loaderImport": "@acme/stencil-lib/loader",
+          "hydrateImport": "@acme/stencil-lib/hydrate"
+        }
+      }
+    }
+  ]
+}
+```
+
+Example config with an explicit manifest override:
+
+```json
+{
+  "projects": [
+    {
+      "id": "demo",
+      "adapter": "stencil",
+      "adapterPackage": "@qwik-custom-elements/adapter-stencil",
+      "source": {
+        "type": "PACKAGE_NAME",
+        "packageName": "@acme/stencil-lib",
+        "cemPath": "dist/custom-elements.json"
+      },
+      "outDir": "./apps/qwik-demo/src/generated/acme",
+      "cleanOutput": true,
+      "adapterOptions": {
+        "runtime": {
+          "loaderImport": "@acme/stencil-lib/loader",
+          "hydrateImport": "@acme/stencil-lib/hydrate"
+        }
+      }
+    }
+  ]
+}
+```
+
+Why use `PACKAGE_NAME`:
+
+- Best fit when the library is installed and consumed like a normal package.
+- Lets the generator resolve the package root and discover the manifest automatically.
+- Keeps config closer to the way end users actually import the library.
+- Works well when package exports are the source of truth for runtime entrypoints.
+
+## `CEM`
+
+Use `CEM` when you want explicit control over the manifest and runtime import locations.
+
+Example config:
+
+```json
+{
+  "projects": [
+    {
+      "id": "demo",
+      "adapter": "stencil",
+      "adapterPackage": "@qwik-custom-elements/adapter-stencil",
+      "source": {
+        "type": "CEM",
+        "path": "./vendor/acme/custom-elements.json"
+      },
+      "outDir": "./apps/qwik-demo/src/generated/acme",
+      "cleanOutput": true,
+      "adapterOptions": {
+        "runtime": {
+          "loaderImport": "@acme/stencil-lib/loader",
+          "hydrateImport": "@acme/stencil-lib/hydrate"
+        }
+      }
+    }
+  ]
+}
+```
+
+Example config where runtime imports point at a project-local shim:
+
+```json
+{
+  "projects": [
+    {
+      "id": "demo",
+      "adapter": "stencil",
+      "adapterPackage": "@qwik-custom-elements/adapter-stencil",
+      "source": {
+        "type": "CEM",
+        "path": "./artifacts/acme/custom-elements.json"
+      },
+      "outDir": "./apps/qwik-demo/src/generated/acme",
+      "cleanOutput": true,
+      "adapterOptions": {
+        "runtime": {
+          "loaderImport": "./src/runtime/acme-loader",
+          "hydrateImport": "./src/runtime/acme-hydrate"
+        }
+      }
+    }
+  ]
+}
+```
+
+Why use `CEM`:
+
+- The Stencil library is not installed as a normal package.
+- You want generation decoupled from package resolution.
+- You need to point at a specific manifest artifact rather than rely on package discovery.
+- Runtime imports come from a shim, wrapper, vendored output, or nonstandard location.
+- You want explicit, reproducible control over both metadata and runtime entrypoints.
+
+## Planned Runtime Discovery Rules
+
+For Stencil generation, the runtime can use two imports in addition to component metadata:
+
+- a loader import used on the client (`defineCustomElements`)
+- a hydrate import used for SSR (`renderToString`)
+
+The current contract is:
+
+- `PACKAGE_NAME` resolves runtime imports to `<packageName>/loader` and `<packageName>/hydrate` by default.
+- For `PACKAGE_NAME`, explicit `adapterOptions.runtime.loaderImport` and `adapterOptions.runtime.hydrateImport` overrides take precedence over those defaults. When an override is set, it must be a non-empty string.
+- For `PACKAGE_NAME`, the resolved loader import must be package-resolvable before generation proceeds. Loader resolution failures stop the run with a deterministic loader-specific error.
+- For `PACKAGE_NAME`, the resolved hydrate import is validated when provided or inferred. Hydrate resolution failures downgrade SSR availability and emit a hydrate-specific diagnostic instead of aborting loader-only generation.
+- `CEM` requires `adapterOptions.runtime.loaderImport`.
+- `CEM` may omit `adapterOptions.runtime.hydrateImport` when SSR hydrate support is unavailable or intentionally deferred.
+- Core consumes the adapter-resolved runtime imports when invoking adapter SSR probing, so runtime resolution and SSR capability checks use the same resolved inputs.
+
+`SSR available` has a specific meaning for Stencil projects:
+
+- The resolved hydrate module can be imported by the probe, and the module exports `renderToString` as a function.
+- If hydrate import fails or `renderToString` is missing/non-function, SSR is treated as unavailable.
+- When SSR is unavailable but the loader import is valid, generation remains successful in loader-only mode with the CSR surface.
+
+This keeps `PACKAGE_NAME` ergonomic while preserving `CEM` as an explicit-control mode for advanced or nonstandard setups.
+
+## Generated Runtime Modules
+
+For Stencil projects with a valid resolved loader import, generated client bootstrap remains valuable even when hydrate-backed SSR is unavailable.
+
+The generated client module (`runtime-csr.generated.ts`) provides:
+
+- a resolved `defineCustomElements` wrapper bound to the package-aware loader import
+- `defineCustomElementsQrl`
+- `useStencilClientSetup`
+- `GeneratedStencilCSRComponent` — the client-only rendering bridge created by `createStencilCSRComponent()`
+
+When a resolved hydrate import is also available, generation additionally emits `runtime-ssr.generated.ts` with a typed `renderToString` export that loads the resolved hydrate runtime through the same Vite-ignored dynamic import boundary used for SSR-safe demo integration.
+
+For `PACKAGE_NAME`, those runtime imports may come from package-aware defaults or explicit overrides. For `CEM`, they come from the explicit `adapterOptions.runtime` contract. This keeps generated runtime modules aligned with the same resolved runtime import contract already used for validation and SSR probing.
+
+The generated runtime exposes two capability-specific consumer surfaces when runtime modes differ materially:
+
+- a CSR surface for loader-only generation that boots the client runtime and backs wrappers with `createStencilCSRComponent`
+- an SSR surface for hydrate-capable generation that includes the hydrate bridge and backs wrappers with `createStencilSSRComponent`
+
+The runtime leaf split is intentional:
+
+- `runtime-csr.generated.ts` is client-reachable and must remain loader-only.
+- `runtime-ssr.generated.ts` owns the hydrate-backed `renderToString` bridge and keeps hydrate loading behind a dynamic import boundary.
+
+Generation mode depends on which resolved runtime imports are actually available, but the final Issue `#34` contract should not require loader-only wrappers to target the same bridge/runtime surface as SSR-capable wrappers:
+
+- Full SSR mode: both loader and hydrate resolve, so generation emits an SSR-capable surface whose wrappers render through `createStencilSSRComponent`.
+- Loader-only mode: loader resolves but hydrate does not, so generation still emits a client-capable surface, but that surface should be backed by `createStencilCSRComponent` rather than a degraded SSR bridge.
+
+When hydrate resolution fails, the client runtime module is still generated from the loader import so loader-only fallback flows remain usable.
+
+## Generated Wrapper Artifacts
+
+When the generator has enough Stencil runtime information, `@qwik-custom-elements/adapter-stencil` owns the full generated surface under the target `outDir`.
+
+For equivalent resolved runtime inputs, `PACKAGE_NAME` and `CEM` projects produce the same consumer-facing wrapper contract. CSR and SSR generation expose distinct surfaces when their runtime behavior diverges.
+
+The generated surface uses a flat structure:
+
+- `index.ts`
+  - Barrel that re-exports each generated Qwik wrapper plus the shared runtime helpers.
+- `runtime.ts`
+  - Stable app-facing barrel that re-exports the generated client and SSR runtime leaves.
+- `runtime-csr.generated.ts`
+  - Client bootstrap module that wires `defineCustomElements` into Qwik-friendly helpers and exports `GeneratedStencilCSRComponent`.
+- `runtime-ssr.generated.ts` (emitted only when hydrate is available)
+  - SSR-only bridge helpers that keep hydrate loading behind a dynamic import boundary.
+- `*.tsx`
+  - One generated Qwik wrapper per discovered Stencil component.
+
+The current behavior:
+
+- loader-only generation emits a CSR surface backed by `createStencilCSRComponent` (no `runtime-ssr.generated.ts`, wrappers render through `GeneratedStencilCSRComponent`)
+- SSR-capable generation additionally emits `runtime-ssr.generated.ts` and backs wrappers with `GeneratedStencilComponent` from the SSR surface
+- exact surface paths are implementation detail
+- wrappers in both modes preserve the same public interface for typed props, typed `onEvent$` bindings, and slot projection
+
+Generated wrapper components follow a stable contract:
+
+- Prop typing starts from available CEM attribute and member metadata.
+- Custom events become typed `onEvent$` QRL props when event metadata is available.
+- Wrapper components call `useStencilClientSetup()` so client bootstrap stays centralized in generated runtime output.
+- When SSR runtime is available, wrappers render through `GeneratedStencilComponent` from the SSR surface backed by `createStencilSSRComponent`.
+- When only the loader runtime is available, wrappers render through `GeneratedStencilCSRComponent` from the CSR surface backed by `createStencilCSRComponent`, rendering the custom-element tag directly while preserving props, typed `onEvent$` bindings, slot metadata, and client bootstrap.
+- Slot metadata is projected with deterministic Qwik `<Slot />` output, including named slot support when the source metadata declares it.
+
+Example generated surface (SSR-capable mode):
+
+```text
+src/generated/
+  index.ts
+  runtime.ts
+  runtime-csr.generated.ts
+  runtime-ssr.generated.ts
+  de-button.tsx
+  de-alert.tsx
+```
+
+In loader-only mode, `runtime-ssr.generated.ts` is not emitted, and wrapper files render through `GeneratedStencilCSRComponent` instead of `GeneratedStencilComponent`.
+
+Example consumer usage:
+
+```tsx
+import { $, component$ } from '@builder.io/qwik';
+
+import { QwikDeAlert, QwikDeButton } from './generated';
+
+export default component$(() => {
+  const handleTripleClick$ = $(() => {
+    console.log('triple click');
+  });
+
+  return (
+    <>
+      <QwikDeButton size="md" onTripleClick$={handleTripleClick$}>
+        Generated Button
+      </QwikDeButton>
+
+      <QwikDeAlert heading="Generated Alert">
+        <span>Default slot content</span>
+        <span q:slot="footer">Named slot content</span>
+      </QwikDeAlert>
+    </>
+  );
+});
+```
+
+The checked-in demo route at `apps/qwik-demo/src/routes/stencil/ssr/wrappers/` is the reference integration path for this generated surface. It validates that generated wrappers, generated runtime setup, typed event handlers, and slot projection all work together without a handwritten app-local bridge layer.
+
+The checked-in CSR demo routes at `apps/qwik-demo/src/routes/stencil/csr/` consume CSR-generated output directly rather than re-exporting or aliasing the SSR demo routes.
+
+## SSR Fallback Behavior
+
+Generation supports SSR where available but does not require SSR availability to produce useful wrappers.
+
+The behavior for Stencil projects is:
+
+- If both loader and hydrate are available, generation emits an SSR-capable surface with both `runtime-csr.generated.ts` and `runtime-ssr.generated.ts`, and wrappers render through `createStencilSSRComponent`.
+- If only loader is available and hydrate/SSR support is unavailable, generation still emits a client-capable CSR surface backed by `createStencilCSRComponent`. The CSR surface omits `runtime-ssr.generated.ts` entirely.
+
+Consumers can treat those two modes as separate capability-specific surfaces with the same wrapper-facing contract:
+
+- Full SSR mode exposes an SSR-capable surface whose wrappers render through `createStencilSSRComponent`.
+- Loader-only mode exposes a CSR surface whose wrappers render through `createStencilCSRComponent` and never depend on Stencil server rendering.
+- In both modes, wrapper props, event bindings, slot projection, and client bootstrap stay adapter-owned and deterministic.
+
+The loader-only fallback still provides value to consumers because generated Qwik components remain:
+
+- typed
+- consistent across components
+- event-aware
+- slot-aware
+- ready for client-side Stencil upgrade
+
+## Documentation Expectations
+
+Consumer-facing behavior for source types, runtime discovery, SSR fallback, and generated output shape should be documented whenever changes land in this adapter or the core generator.
+
+Architecture ownership changes should also keep this README aligned with the package-level boundary: Stencil-specific generated output belongs here, not in `@qwik-custom-elements/core`.

package/dist/bundle-graph.json

@@ -0,0 +1 @@
+["../client-setup-C_qW_ZSR.cjs",9,-9,4,"../client-setup.ts_createStencilClientSetup_runSetup_6wDTmOSdSbc-Dz0z3zer.cjs",0,"../client/index.cjs",0,12,"../core.min-vJ4M2jcU.cjs","../ssr/index.cjs",25,"../stencil-csr-D6zt1Am9.cjs",9,-9,16,"../stencil-csr.tsx_createStencilCSRComponent_component_pD3ekIZcUT0-cGN__hqm.cjs",9,-8,21,23,"../stencil-csr.tsx_createStencilCSRComponent_component_useVisibleTask_1_dqWPXf9eNnk-sFN0uMI_.cjs",12,"../stencil-csr.tsx_createStencilCSRComponent_component_useVisibleTask_y00qkhhKua8-BSsN2V78.cjs",9,"../stencil-ssr-UlYtcG0-.cjs",9,-9,29,"../stencil-ssr.tsx_createStencilSSRBridgeComponent_component_IlVdOHKZfN0-46y8eTjO.cjs",9,-8,38,40,-6,36,"../stencil-ssr.tsx_createStencilSSRBridgeComponent_component_useOnDocument_bvALMlewx7Q-DA73DRke.cjs",9,"../stencil-ssr.tsx_createStencilSSRBridgeComponent_component_useTask_1_aXg7AuatGTc-61dSP-JG.cjs",25,"../stencil-ssr.tsx_createStencilSSRBridgeComponent_component_useTask_IH8I3eLdwI0-DNQBT8Vc.cjs",10,"IH8I3eLdwI0",-8,40,"aXg7AuatGTc",-8,38,"dqWPXf9eNnk",-8,21,"y00qkhhKua8",-8,23,"IlVdOHKZfN0",-7,29,"pD3ekIZcUT0",-7,16,"6wDTmOSdSbc",-6,4,"bvALMlewx7Q",-6,36]

package/dist/client/client-setup.d.ts

@@ -0,0 +1,9 @@
+import { type QRL } from '@builder.io/qwik';
+type DefineCustomElementsInput = QRL<() => Promise<void>> | (() => Promise<void>);
+/**
+ * Creates a client-side setup hook for Stencil components.
+ * Promotes SSR-emitted styles into document head, then registers custom elements.
+ */
+export declare function createStencilClientSetup(defineCustomElementsInput?: DefineCustomElementsInput): () => void;
+export {};
+//# sourceMappingURL=client-setup.d.ts.map

package/dist/client/client-setup.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"client-setup.d.ts","sourceRoot":"","sources":["../../src/client/client-setup.ts"],"names":[],"mappings":"AAAA,OAAO,EAAoB,KAAK,GAAG,EAAE,MAAM,kBAAkB,CAAC;AAS9D,KAAK,yBAAyB,GAC1B,GAAG,CAAC,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC,GACxB,CAAC,MAAM,OAAO,CAAC,IAAI,CAAC,CAAC,CAAC;AA2H1B;;;GAGG;AACH,wBAAgB,wBAAwB,CACtC,yBAAyB,CAAC,EAAE,yBAAyB,cAgCtD"}

package/dist/client/client-setup.test.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=client-setup.test.d.ts.map

package/dist/client/client-setup.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"client-setup.test.d.ts","sourceRoot":"","sources":["../../src/client/client-setup.test.ts"],"names":[],"mappings":""}

package/dist/client/index.cjs

@@ -0,0 +1 @@
+"use strict";Object.defineProperty(exports,Symbol.toStringTag,{value:"Module"});const e=require("../client-setup-C_qW_ZSR.cjs"),t=require("../stencil-csr-D6zt1Am9.cjs");exports.createStencilClientSetup=e.createStencilClientSetup;exports.createStencilCSRComponent=t.createStencilCSRComponent;

package/dist/client/index.d.ts

@@ -0,0 +1,3 @@
+export { createStencilClientSetup } from './client-setup';
+export { createStencilCSRComponent, type StencilCSRProps } from './stencil-csr';
+//# sourceMappingURL=index.d.ts.map

package/dist/client/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/client/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,wBAAwB,EAAE,MAAM,gBAAgB,CAAC;AAC1D,OAAO,EAAE,yBAAyB,EAAE,KAAK,eAAe,EAAE,MAAM,eAAe,CAAC"}

package/dist/client/index.js

@@ -0,0 +1,6 @@
+import { c } from "../client-setup-D-ffVtNL.js";
+import { c as r } from "../stencil-csr-B1U9s3VQ.js";
+export {
+  r as createStencilCSRComponent,
+  c as createStencilClientSetup
+};

package/dist/client/stencil-csr-props.d.ts

@@ -0,0 +1,2 @@
+export declare function updateStencilCSRHostProps(host: HTMLElement | undefined, props: Record<string, unknown> | undefined): void;
+//# sourceMappingURL=stencil-csr-props.d.ts.map

package/dist/client/stencil-csr-props.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"stencil-csr-props.d.ts","sourceRoot":"","sources":["../../src/client/stencil-csr-props.ts"],"names":[],"mappings":"AAUA,wBAAgB,yBAAyB,CACvC,IAAI,EAAE,WAAW,GAAG,SAAS,EAC7B,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,SAAS,QAa3C"}

package/dist/client/stencil-csr-props.test.d.ts

@@ -0,0 +1,2 @@
+export {};
+//# sourceMappingURL=stencil-csr-props.test.d.ts.map

package/dist/client/stencil-csr-props.test.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"stencil-csr-props.test.d.ts","sourceRoot":"","sources":["../../src/client/stencil-csr-props.test.ts"],"names":[],"mappings":""}

package/dist/client/stencil-csr.d.ts

@@ -0,0 +1,10 @@
+import { type QRL } from '@builder.io/qwik';
+export interface StencilCSRProps {
+    tagName: string;
+    props?: Record<string, unknown>;
+    events?: Record<string, QRL<(...args: any[]) => void>>;
+    slots?: string[];
+    [key: string]: unknown;
+}
+export declare function createStencilCSRComponent(): import("@builder.io/qwik").Component<StencilCSRProps>;
+//# sourceMappingURL=stencil-csr.d.ts.map

package/dist/client/stencil-csr.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"stencil-csr.d.ts","sourceRoot":"","sources":["../../src/client/stencil-csr.tsx"],"names":[],"mappings":"AAAA,OAAO,EAKL,KAAK,GAAG,EACT,MAAM,kBAAkB,CAAC;AAwC1B,MAAM,WAAW,eAAe;IAC9B,OAAO,EAAE,MAAM,CAAC;IAChB,KAAK,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC;IAChC,MAAM,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,GAAG,CAAC,CAAC,GAAG,IAAI,EAAE,GAAG,EAAE,KAAK,IAAI,CAAC,CAAC,CAAC;IACvD,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;IACjB,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAC;CACxB;AAED,wBAAgB,yBAAyB,0DA0ExC"}

package/dist/client-setup-C_qW_ZSR.cjs

@@ -0,0 +1 @@
+"use strict";const i=require("./core.min-vJ4M2jcU.cjs"),r="__qce_stencil_client_setup_done__",s=new Map;let u=0;function a(e){if(!e)return;const t=`stencil-client-setup-${++u}`;return s.set(t,e),t}async function d(e){if(e)return typeof e=="object"&&e!==null&&"resolve"in e&&typeof e.resolve=="function"?e.resolve():e}async function S(e){const t=document.querySelectorAll("style[sty-id]"),n=new Set;for(const o of t)if(o.parentElement!==document.head){const c=o.textContent??"";n.has(c)?o.remove():(document.head.appendChild(o),n.add(c))}e&&await e()}function f(e){const t=globalThis,n=t[r];if(n===!0)return Promise.resolve();if(typeof n=="object"&&n!==null&&"then"in n&&typeof n.then=="function")return n;const o=(async()=>{const c=await d(e);await S(c)})();return t[r]=o,o.then(()=>{t[r]=!0}).catch(c=>{throw delete t[r],c})}async function l(e,t){const o=(e==null?void 0:s.get(e))??t;await f(o).catch(c=>{console.error(c)})}function p(e){const t=a(e),n=e!=null&&"$symbol$"in Object(e)?e:void 0,o=i.Ls(()=>Promise.resolve().then(()=>require("./client-setup.ts_createStencilClientSetup_runSetup_6wDTmOSdSbc-Dz0z3zer.cjs")),"s_6wDTmOSdSbc",[t,n]);return()=>{i.Re("load",o),typeof document<"u"&&document.readyState!=="loading"&&l(t,n)}}exports.createStencilClientSetup=p;exports.executeStencilClientSetup=l;

package/dist/client-setup-D-ffVtNL.js

@@ -0,0 +1,53 @@
+import { R as i, L as l } from "./core.min-Qm7Mxv6F.js";
+const r = "__qce_stencil_client_setup_done__", s = /* @__PURE__ */ new Map();
+let u = 0;
+function a(e) {
+  if (!e) return;
+  const t = `stencil-client-setup-${++u}`;
+  return s.set(t, e), t;
+}
+async function d(e) {
+  if (e)
+    return typeof e == "object" && e !== null && "resolve" in e && typeof e.resolve == "function" ? e.resolve() : e;
+}
+async function f(e) {
+  const t = document.querySelectorAll("style[sty-id]"), n = /* @__PURE__ */ new Set();
+  for (const o of t) if (o.parentElement !== document.head) {
+    const c = o.textContent ?? "";
+    n.has(c) ? o.remove() : (document.head.appendChild(o), n.add(c));
+  }
+  e && await e();
+}
+function S(e) {
+  const t = globalThis, n = t[r];
+  if (n === !0) return Promise.resolve();
+  if (typeof n == "object" && n !== null && "then" in n && typeof n.then == "function") return n;
+  const o = (async () => {
+    const c = await d(e);
+    await f(c);
+  })();
+  return t[r] = o, o.then(() => {
+    t[r] = !0;
+  }).catch((c) => {
+    throw delete t[r], c;
+  });
+}
+async function p(e, t) {
+  const o = (e == null ? void 0 : s.get(e)) ?? t;
+  await S(o).catch((c) => {
+    console.error(c);
+  });
+}
+function m(e) {
+  const t = a(e), n = e != null && "$symbol$" in Object(e) ? e : void 0, o = /* @__PURE__ */ l(() => import("./client-setup.ts_createStencilClientSetup_runSetup_6wDTmOSdSbc-CPKK-h2J.js"), "s_6wDTmOSdSbc", [
+    t,
+    n
+  ]);
+  return () => {
+    i("load", o), typeof document < "u" && document.readyState !== "loading" && p(t, n);
+  };
+}
+export {
+  m as c,
+  p as e
+};

package/dist/client-setup.ts_createStencilClientSetup_runSetup_6wDTmOSdSbc-CPKK-h2J.js

@@ -0,0 +1,11 @@
+import { v as o } from "./core.min-Qm7Mxv6F.js";
+import { x as p } from "./core.min-Qm7Mxv6F.js";
+import { e as n } from "./client-setup-D-ffVtNL.js";
+const m = async () => {
+  const [t, e] = o();
+  await n(t, e);
+};
+export {
+  p as _hW,
+  m as s_6wDTmOSdSbc
+};

package/dist/client-setup.ts_createStencilClientSetup_runSetup_6wDTmOSdSbc-Dz0z3zer.cjs

@@ -0,0 +1 @@
+"use strict";Object.defineProperty(exports,Symbol.toStringTag,{value:"Module"});const e=require("./core.min-vJ4M2jcU.cjs"),c=require("./client-setup-C_qW_ZSR.cjs"),i=async()=>{const[t,n]=e.ve();await c.executeStencilClientSetup(t,n)};exports._hW=e.xe;exports.s_6wDTmOSdSbc=i;