@embedpdf/viewer-svelte 0.0.0-stage → 3.0.0-next.16

package/LICENSE

@@ -0,0 +1,192 @@
+Copyright 2026 CloudPDF LTD
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use files in this distribution except in compliance with the License.
+You may obtain a copy of the License at
+
+    https://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.
+
+-----------------------------------------------------------------------
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS

package/README.md

@@ -1,3 +1,78 @@
-# Temporary Holding Version
+# @embedpdf/viewer-svelte
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+The full EmbedPDF viewer as a Svelte 5 component: a thin wrapper around the
+`<embedpdf-viewer>` custom element from [`@embedpdf/viewer`](https://www.npmjs.com/package/@embedpdf/viewer).
+
+```bash
+npm install @embedpdf/viewer-svelte
+```
+
+```svelte
+<script lang="ts">
+  import { PDFViewer } from '@embedpdf/viewer-svelte';
+</script>
+
+<PDFViewer src="/report.pdf" style="height: 100vh" />
+```
+
+No engine or wasm configuration is needed: the built-in local engine (PDFium
+compiled to WebAssembly, running in a Web Worker) is the default, and your
+bundler ships `embedpdf.wasm` inside your own build. Self-hosting, strict-CSP
+worker delivery, and injecting a different engine implementation are all
+available through the `engine` prop — see the docs.
+
+## Your own components
+
+`ToolbarItem`, `Panel` and `Region` put your component in the place the layout
+makes for it, while it stays in **your** Svelte app — your context, your
+state, your CSS:
+
+```svelte
+<script lang="ts">
+  import { PDFViewer, ToolbarItem, type Layout } from '@embedpdf/viewer-svelte';
+  import DocPicker from './DocPicker.svelte';
+
+  const layout = (layout: Layout) => layout.add({ custom: 'doc-picker' }, { to: 'main', section: 'start' });
+</script>
+
+<PDFViewer src="/report.pdf" {layout}>
+  <ToolbarItem id="doc-picker"><DocPicker /></ToolbarItem>
+</PDFViewer>
+```
+
+`useToolbarItem()` tells it where it sits, and `Button`, `Menu` and `MenuItem`
+are the viewer's own, for yours.
+
+## Driving the viewer
+
+```svelte
+<PDFViewer src="/report.pdf" onready={(viewer) => viewer.commands.execute('zoom:in')} />
+```
+
+`onready` hands you the `viewer`: each plugin's API by its name
+(`viewer.get('search')`, or its token), `viewer.documents`, `viewer.commands`
+and the `watch` reactivity primitive. Inside the viewer, a component of yours
+gets it with `usePDFViewer()`, and `useCommand(id)` gives it a command as a
+button needs it (label, icon, shortcut, state and `run()`). The headless
+functions of `@embedpdf/svelte` work there too. `ondocumentchange` and
+`onpanelresize` say when the active document changes and when someone resizes
+a panel. When the viewer unmounts, its `viewer` is done: its listeners stop and
+its calls refuse.
+
+`src`, `theme`, `locale`, `disable` and `readOnly` follow their props while the
+viewer runs; every other prop is read once, so wrap the viewer in `{#key}` to
+start over with a changed one.
+
+## Server-side rendering
+
+Safe to import and render on the server (SvelteKit included, no
+`{#if browser}`): `<PDFViewer>` renders the empty `<embedpdf-viewer>` element,
+and the viewer starts in the browser.
+
+## Documentation
+
+Full guides and API reference: https://www.embedpdf.com/docs
+
+## License
+
+Apache-2.0

package/dist/component.svelte

@@ -0,0 +1,105 @@
+<!--
+  <PDFViewer>: the Svelte face of the <embedpdf-viewer> custom element, and engine-blind: it
+  imports the viewer for types only, so it holds no runtime edge to any engine. Which engine ships
+  is decided by the entry that re-exports it: `./index.ts` imports `@embedpdf/viewer` (the built-in
+  local engine, registered as the default), `./core.ts` imports `@embedpdf/viewer/core` (no default
+  engine: you give one, and PDFium is not in the module graph). That one import is the whole
+  difference between the two doors, and it lives only in those two files.
+
+  It renders the element and gives it the config before the element's deferred first mount, so the
+  viewer starts once, with it. `src`, `theme`, `locale`, `disable` and `readOnly` follow their
+  props: the element changes them in place, comparing by value. Every other prop is read once: a
+  later change is ignored (development warns), and a `{#key}` block mounts a new viewer with it.
+  `onready`, `ondocumentchange` and `onpanelresize` call the latest prop.
+
+  Your components are its children, light DOM the browser shows in the viewer's slots while they
+  stay in your Svelte tree, with your context, state and CSS. They mount once the viewer is ready,
+  inside its kernel, so the headless functions of `@embedpdf/svelte` in them read this viewer, and
+  `usePDFViewer()` gives them its `viewer`. When the viewer goes they unmount with it, and mount
+  again inside the next one. On the server it renders the empty element, and the viewer starts in
+  the browser.
+-->
+<script lang="ts">
+  import { DEV } from 'esm-env';
+  import { untrack } from 'svelte';
+  // The headless runtime carries no engine: it gives the children the viewer's kernel.
+  import { KernelProvider, type Kernel } from '@embedpdf/svelte/runtime';
+  // `ElementConfig` is the kernel's config, the widest of all, with the engine seam `unknown`: the
+  // shared implementation sits above every door, and each entry narrows it by assignment.
+  import type { ElementConfig, Viewer } from '@embedpdf/viewer/core';
+  import { changedReadOnceKey, liveConfigOf, readOnceWarning } from './config.js';
+  import { setViewerContext } from './hooks.js';
+  import type { PDFViewerImplProps } from './props.js';
+
+  let {
+    class: className,
+    style,
+    children,
+    element = $bindable(null),
+    onready,
+    ondocumentchange,
+    onpanelresize,
+    ...config
+  }: PDFViewerImplProps = $props();
+
+  // The viewer once it's ready: the children render inside its kernel. Before that the viewer has
+  // no slots to show them in.
+  let viewer = $state.raw<Viewer | null>(null);
+  setViewerContext(() => viewer);
+
+  /** Where the viewer keeps its kernel (`createViewer` in `@embedpdf/viewer-chrome`). */
+  const VIEWER_KERNEL = Symbol.for('@embedpdf/viewer/kernel');
+  const kernel = $derived(
+    viewer ? ((viewer as unknown as Partial<Record<symbol, Kernel>>)[VIEWER_KERNEL] ?? null) : null,
+  );
+
+  // The config the viewer starts with: the props as they are now, read once. The callbacks reach
+  // the element once too, as functions that read the prop when they're called, so an inline
+  // handler that changes is the one called.
+  const initial = untrack(() => ({ ...config }));
+  const started: ElementConfig = {
+    ...initial,
+    onReady: (ready) => {
+      viewer = ready;
+      onready?.(ready);
+    },
+    onDocumentChange: (documentId) => ondocumentchange?.(documentId),
+    onPanelResize: (event) => onpanelresize?.(event),
+  };
+
+  // The element's attributes and properties. Svelte sets a property while it creates the element,
+  // before the element is on the page, so `config` is there for its first mount; the live keys are
+  // set again when they change, and the element compares them by value (an inline array is no
+  // change). On the server there are no properties: it renders the empty element.
+  const attributes = $derived({
+    class: className,
+    style,
+    ...(typeof document === 'undefined' ? {} : { config: started, ...liveConfigOf(config) }),
+  });
+
+  // Every other prop is read once: say so, once, when one changes after the viewer started.
+  // A development build, as Svelte itself reads it.
+  if (DEV) {
+    let warned = false;
+    $effect(() => {
+      if (warned) return;
+      const key = changedReadOnceKey(initial, { ...config });
+      if (key === null) return;
+      warned = true;
+      console.warn(readOnceWarning(key));
+    });
+  }
+</script>
+
+<!-- The element waits for the config set here, also over the server's HTML before hydration. -->
+<embedpdf-viewer bind:this={element} data-epdf-wrapped="" {...attributes}>
+  {#if viewer}
+    {#key viewer}
+      {#if kernel}
+        <KernelProvider {kernel}>{@render children?.()}</KernelProvider>
+      {:else}
+        {@render children?.()}
+      {/if}
+    {/key}
+  {/if}
+</embedpdf-viewer>

package/dist/component.svelte.d.ts

@@ -0,0 +1,4 @@
+import type { PDFViewerImplProps } from './props.js';
+declare const Component: import("svelte").Component<PDFViewerImplProps, {}, "element">;
+type Component = ReturnType<typeof Component>;
+export default Component;

package/dist/config.d.ts

@@ -0,0 +1,20 @@
+/**
+ * How `<PDFViewer>` treats its config: the live keys it hands on to the running viewer, and the
+ * rest, read once, with a warning in development when one changes.
+ */
+import type { LiveConfigKey } from '@embedpdf/viewer/core';
+/** The live keys of `config`, as the element's properties of the same names take them. */
+export declare function liveConfigOf(config: Partial<Record<LiveConfigKey, unknown>>): {
+    src: unknown;
+    theme: unknown;
+    locale: unknown;
+    disable: unknown;
+    readOnly: unknown;
+};
+/**
+ * The first key, other than the live ones, whose value isn't the one the viewer started with, or
+ * null. By identity: Svelte keeps a prop's value until what it's made from changes.
+ */
+export declare function changedReadOnceKey(started: object, current: object): string | null;
+/** What development says when a read-once key changes. */
+export declare const readOnceWarning: (key: string) => string;

package/dist/config.js

@@ -0,0 +1,37 @@
+/** The keys the element follows while it runs: `<PDFViewer>` hands their changes on. */
+const LIVE_KEYS = {
+    src: true,
+    theme: true,
+    locale: true,
+    disable: true,
+    readOnly: true,
+};
+/** The live keys of `config`, as the element's properties of the same names take them. */
+export function liveConfigOf(config) {
+    return {
+        src: config.src,
+        theme: config.theme,
+        locale: config.locale,
+        disable: config.disable,
+        readOnly: config.readOnly,
+    };
+}
+/**
+ * The first key, other than the live ones, whose value isn't the one the viewer started with, or
+ * null. By identity: Svelte keeps a prop's value until what it's made from changes.
+ */
+export function changedReadOnceKey(started, current) {
+    const before = started;
+    const after = current;
+    for (const key of new Set([...Object.keys(before), ...Object.keys(after)])) {
+        if (key in LIVE_KEYS)
+            continue;
+        if (!Object.is(before[key], after[key]))
+            return key;
+    }
+    return null;
+}
+/** What development says when a read-once key changes. */
+export const readOnceWarning = (key) => `[embedpdf] <PDFViewer>: \`${key}\` is read once, when the viewer starts, so the change is ` +
+    'ignored. Pass a stable value (module scope, or $state that keeps it), or put the viewer in a ' +
+    '{#key} block to mount a new one with it.';

package/dist/core.d.ts

@@ -0,0 +1,33 @@
+/**
+ * @embedpdf/viewer-svelte/core — the engine-agnostic Svelte door.
+ *
+ * ```svelte
+ * <script lang="ts">
+ *   import { PDFViewer } from '@embedpdf/viewer-svelte/core';
+ *   import { cloudEngine } from '@cloudpdf/engine';
+ * </script>
+ *
+ * <PDFViewer engine={() => cloudEngine({ baseUrl, token })} {documents} />
+ * ```
+ *
+ * The same `<PDFViewer>` as the main entry, but with no default engine: `engine` is required, and
+ * takes only a real implementation (an `Engine`, or a function the viewer owns the lifetime of).
+ * In exchange the local PDFium engine (wasm, worker source, main-thread recipe) never enters your
+ * module graph: nothing is stubbed or aliased away, it is not imported. Its options are absent
+ * from the type for the same reason: there is no built-in engine here for `{ assetsUrl }` to
+ * configure.
+ *
+ * App code that wants the batteries-included viewer imports `@embedpdf/viewer-svelte`; this entry
+ * is for builds that always give their own engine, and is what the CloudPDF Svelte wrapper is
+ * built on.
+ */
+import '@embedpdf/viewer/core';
+import type { ViewerConfig } from '@embedpdf/viewer/core';
+import type { Component } from 'svelte';
+import { type PDFViewerPropsOf } from './parts.js';
+export * from '@embedpdf/viewer/core';
+export * from './parts.js';
+/** Props on this door: `engine` is required, and only a real engine satisfies it. */
+export type PDFViewerProps = PDFViewerPropsOf<ViewerConfig>;
+/** The shared component, narrowed to this door's config: the wider props type assigns to it. */
+export declare const PDFViewer: Component<PDFViewerProps, {}, 'element'>;

package/dist/core.js

@@ -0,0 +1,29 @@
+/**
+ * @embedpdf/viewer-svelte/core — the engine-agnostic Svelte door.
+ *
+ * ```svelte
+ * <script lang="ts">
+ *   import { PDFViewer } from '@embedpdf/viewer-svelte/core';
+ *   import { cloudEngine } from '@cloudpdf/engine';
+ * </script>
+ *
+ * <PDFViewer engine={() => cloudEngine({ baseUrl, token })} {documents} />
+ * ```
+ *
+ * The same `<PDFViewer>` as the main entry, but with no default engine: `engine` is required, and
+ * takes only a real implementation (an `Engine`, or a function the viewer owns the lifetime of).
+ * In exchange the local PDFium engine (wasm, worker source, main-thread recipe) never enters your
+ * module graph: nothing is stubbed or aliased away, it is not imported. Its options are absent
+ * from the type for the same reason: there is no built-in engine here for `{ assetsUrl }` to
+ * configure.
+ *
+ * App code that wants the batteries-included viewer imports `@embedpdf/viewer-svelte`; this entry
+ * is for builds that always give their own engine, and is what the CloudPDF Svelte wrapper is
+ * built on.
+ */
+import '@embedpdf/viewer/core';
+import { PDFViewer as PDFViewerImpl } from './parts.js';
+export * from '@embedpdf/viewer/core';
+export * from './parts.js';
+/** The shared component, narrowed to this door's config: the wider props type assigns to it. */
+export const PDFViewer = PDFViewerImpl;

package/dist/hooks.d.ts

@@ -0,0 +1,21 @@
+/**
+ * The functions for components inside `<PDFViewer>`: the `viewer`, and a command as a button
+ * needs it. They work in the components you give the viewer, which mount once it's live, inside
+ * it. The headless functions of `@embedpdf/svelte` work there too, for any plugin's API and state.
+ */
+import type { Viewer } from '@embedpdf/viewer/core';
+/**
+ * A command as a button needs it, for the active document, as `{ current }`: its `label`, `icon`
+ * and `shortcut`, whether it's `enabled`, `active` and `visible`, and `run()`. The headless
+ * function, which reads the kernel `<PDFViewer>` gives its children: an id the viewer doesn't
+ * have is neither visible nor enabled.
+ */
+export { useCommand } from '@embedpdf/svelte/commands';
+/** For `<PDFViewer>`: give the components inside it the viewer `current()` says is live. */
+export declare function setViewerContext(current: () => Viewer | null): void;
+/**
+ * The `viewer`, in a component inside `<PDFViewer>`: `get(name)`, `documents`, `commands`,
+ * `watch` and `forDocument`. Your components mount once the viewer is live, so it is always
+ * there. Outside the viewer, keep the one `onready` gives you; called there, this throws.
+ */
+export declare function usePDFViewer(): Viewer;

package/dist/hooks.js

@@ -0,0 +1,27 @@
+import { getContext, hasContext, setContext, untrack } from 'svelte';
+/**
+ * A command as a button needs it, for the active document, as `{ current }`: its `label`, `icon`
+ * and `shortcut`, whether it's `enabled`, `active` and `visible`, and `run()`. The headless
+ * function, which reads the kernel `<PDFViewer>` gives its children: an id the viewer doesn't
+ * have is neither visible nor enabled.
+ */
+export { useCommand } from '@embedpdf/svelte/commands';
+const VIEWER = Symbol('embedpdf.pdf-viewer');
+/** For `<PDFViewer>`: give the components inside it the viewer `current()` says is live. */
+export function setViewerContext(current) {
+    setContext(VIEWER, current);
+}
+/**
+ * The `viewer`, in a component inside `<PDFViewer>`: `get(name)`, `documents`, `commands`,
+ * `watch` and `forDocument`. Your components mount once the viewer is live, so it is always
+ * there. Outside the viewer, keep the one `onready` gives you; called there, this throws.
+ */
+export function usePDFViewer() {
+    // Untracked: the components inside mount again for a new viewer, so this one never changes.
+    const viewer = hasContext(VIEWER) ? untrack(getContext(VIEWER)) : null;
+    if (!viewer) {
+        throw new Error('[embedpdf] usePDFViewer() works in a component inside <PDFViewer>. Outside the viewer, ' +
+            'keep the viewer its onready gives you.');
+    }
+    return viewer;
+}

package/dist/index.d.ts

@@ -0,0 +1,28 @@
+/**
+ * @embedpdf/viewer-svelte — the full viewer as a Svelte component, with the built-in local engine
+ * (PDFium wasm in a worker) as the default.
+ *
+ * ```svelte
+ * <script lang="ts">
+ *   import { PDFViewer } from '@embedpdf/viewer-svelte';
+ * </script>
+ *
+ * <PDFViewer src="/report.pdf" style="height: 100vh" />
+ * ```
+ *
+ * Zero config: no `engine` prop, no bundler setup. This is the door app code should use. Builds
+ * that always give their own engine (a cloud deployment, a self-hosted `@cloudpdf/server`) import
+ * `@embedpdf/viewer-svelte/core` instead, which is the same component with PDFium absent.
+ *
+ * The component itself lives in `./component.svelte` and is engine-blind; the one import below is
+ * what makes this entry the local-engine door.
+ */
+import '@embedpdf/viewer';
+import type { ViewerConfig } from '@embedpdf/viewer';
+import type { Component } from 'svelte';
+import { type PDFViewerPropsOf } from './parts.js';
+export * from '@embedpdf/viewer';
+export * from './parts.js';
+export type PDFViewerProps = PDFViewerPropsOf<ViewerConfig>;
+/** The shared component, narrowed to this door's config: the wider props type assigns to it. */
+export declare const PDFViewer: Component<PDFViewerProps, {}, 'element'>;

package/dist/index.js

@@ -0,0 +1,25 @@
+/**
+ * @embedpdf/viewer-svelte — the full viewer as a Svelte component, with the built-in local engine
+ * (PDFium wasm in a worker) as the default.
+ *
+ * ```svelte
+ * <script lang="ts">
+ *   import { PDFViewer } from '@embedpdf/viewer-svelte';
+ * </script>
+ *
+ * <PDFViewer src="/report.pdf" style="height: 100vh" />
+ * ```
+ *
+ * Zero config: no `engine` prop, no bundler setup. This is the door app code should use. Builds
+ * that always give their own engine (a cloud deployment, a self-hosted `@cloudpdf/server`) import
+ * `@embedpdf/viewer-svelte/core` instead, which is the same component with PDFium absent.
+ *
+ * The component itself lives in `./component.svelte` and is engine-blind; the one import below is
+ * what makes this entry the local-engine door.
+ */
+import '@embedpdf/viewer';
+import { PDFViewer as PDFViewerImpl } from './parts.js';
+export * from '@embedpdf/viewer';
+export * from './parts.js';
+/** The shared component, narrowed to this door's config: the wider props type assigns to it. */
+export const PDFViewer = PDFViewerImpl;

package/dist/parts.d.ts

@@ -0,0 +1,15 @@
+/**
+ * @embedpdf/viewer-svelte/component — the wrapper's door-blind parts: `<PDFViewer>` at the widest
+ * config (the kernel's `ElementConfig`), and the components and hooks every door shares.
+ *
+ * A door imports its engine's door, re-exports these, and narrows `<PDFViewer>` to its own
+ * `ViewerConfig` by assignment: this package's two (`.` with the built-in engine, `./core` with
+ * none) and `@cloudpdf/viewer-svelte` with the cloud engine (docs/conventions/viewer-doors.md).
+ */
+export { default as PDFViewer } from './component.svelte';
+export type { PDFViewerExtras, PDFViewerPropsOf } from './props.js';
+export { useCommand, usePDFViewer } from './hooks.js';
+export { Panel, Region, ToolbarItem, useToolbarItem } from './slots.js';
+export type { PanelProps, RegionName, RegionProps, ToolbarItemProps } from './slots.js';
+export { Button, Menu, MenuItem } from './viewer-components.js';
+export type { ButtonProps, MenuItemProps, MenuProps } from './viewer-components.js';

package/dist/parts.js

@@ -0,0 +1,12 @@
+/**
+ * @embedpdf/viewer-svelte/component — the wrapper's door-blind parts: `<PDFViewer>` at the widest
+ * config (the kernel's `ElementConfig`), and the components and hooks every door shares.
+ *
+ * A door imports its engine's door, re-exports these, and narrows `<PDFViewer>` to its own
+ * `ViewerConfig` by assignment: this package's two (`.` with the built-in engine, `./core` with
+ * none) and `@cloudpdf/viewer-svelte` with the cloud engine (docs/conventions/viewer-doors.md).
+ */
+export { default as PDFViewer } from './component.svelte';
+export { useCommand, usePDFViewer } from './hooks.js';
+export { Panel, Region, ToolbarItem, useToolbarItem } from './slots.js';
+export { Button, Menu, MenuItem } from './viewer-components.js';

package/dist/props.d.ts

@@ -0,0 +1,45 @@
+/**
+ * The props of `<PDFViewer>`: every key of the viewer's config, its callbacks under their Svelte
+ * names, and what places it on your page. Types only from the viewer, as in `./component.svelte`:
+ * this module is shared by both doors.
+ */
+import type { ElementConfig, EmbedPdfViewerElement, PanelResizeEvent, Viewer } from '@embedpdf/viewer/core';
+import type { Snippet } from 'svelte';
+/** The framework-side props: everything that is not viewer config. */
+export interface PDFViewerExtras {
+    class?: string;
+    style?: string;
+    /** Your components, shown where their slot says: `<ToolbarItem>`, `<Panel>`, `<Region>`. */
+    children?: Snippet;
+    /** The `<embedpdf-viewer>` element, for its imperative surface: `bind:element`. */
+    element?: EmbedPdfViewerElement | null;
+    /**
+     * Called with the `viewer` once it's live, before any document has opened: capabilities
+     * resolve from then on, and document-scoped calls wait for their document.
+     */
+    onready?: (viewer: Viewer) => void;
+    /**
+     * Called with the active document's id whenever it changes: the first document that opens, a
+     * switch to another tab, and `null` once the last one closes.
+     */
+    ondocumentchange?: (documentId: string | null) => void;
+    /**
+     * Called when the user has resized a panel, with its id and new width in px: once a drag of its
+     * edge ends, and on each arrow key there.
+     */
+    onpanelresize?: (event: PanelResizeEvent) => void;
+}
+/** The config's callbacks, which `<PDFViewer>` takes under their Svelte names. */
+type ConfigCallback = 'onReady' | 'onDocumentChange' | 'onPanelResize';
+/**
+ * The props of `<PDFViewer>` for a door whose config is `Config`: each key of the config is a prop,
+ * except its callbacks, which are `onready`, `ondocumentchange` and `onpanelresize` here, with
+ * `class`, `style`, `children` and `element` next to them.
+ */
+export type PDFViewerPropsOf<Config extends object> = Omit<Config, ConfigCallback> & PDFViewerExtras;
+/**
+ * Props for the shared implementation. Each entry re-exports `<PDFViewer>` narrowed to its door's
+ * config: `PDFViewerProps` in `./index.ts` (engine optional) and `./core.ts` (engine required).
+ */
+export type PDFViewerImplProps = PDFViewerPropsOf<ElementConfig>;
+export {};

package/dist/props.js

@@ -0,0 +1 @@
+export {};

package/dist/slots/Panel.svelte

@@ -0,0 +1,15 @@
+<!--
+  What goes inside one of your panels, the one `addPanel(id, …)` adds to the layout: the viewer
+  draws its frame, its header and the way it opens. It renders as a child of the <embedpdf-viewer>
+  element with the slot `panel:<id>`, in an element that adds no box.
+-->
+<script lang="ts">
+  import type { PanelProps } from './props.js';
+
+  let { id, children }: PanelProps = $props();
+
+  // Spread, `slot` is the element's attribute: written out, Svelte reads it as a slot of its own.
+  const slot = $derived({ slot: `panel:${id}` });
+</script>
+
+<div {...slot} style="display: contents">{@render children?.()}</div>

package/dist/slots/Panel.svelte.d.ts

@@ -0,0 +1,4 @@
+import type { PanelProps } from './props.js';
+declare const Panel: import("svelte").Component<PanelProps, {}, "">;
+type Panel = ReturnType<typeof Panel>;
+export default Panel;

package/dist/slots/Region.svelte

@@ -0,0 +1,15 @@
+<!--
+  Your component in one of the viewer's regions: `header`, `footer`, `tabs` or `empty`. It renders
+  as a child of the <embedpdf-viewer> element with the region's name for its slot, in an element
+  that adds no box.
+-->
+<script lang="ts">
+  import type { RegionProps } from './props.js';
+
+  let { name, children }: RegionProps = $props();
+
+  // Spread, `slot` is the element's attribute: written out, Svelte reads it as a slot of its own.
+  const slot = $derived({ slot: name });
+</script>
+
+<div {...slot} style="display: contents">{@render children?.()}</div>

package/dist/slots/Region.svelte.d.ts

@@ -0,0 +1,4 @@
+import type { RegionProps } from './props.js';
+declare const Region: import("svelte").Component<RegionProps, {}, "">;
+type Region = ReturnType<typeof Region>;
+export default Region;

package/dist/slots/ToolbarItem.svelte

@@ -0,0 +1,27 @@
+<!--
+  Your component in the toolbar, where the layout's `{ custom: id }` makes room for it. It renders
+  as a child of the <embedpdf-viewer> element with the slot `item:<id>`, in an element that adds
+  no box, so it stays in your Svelte tree and lays out in the bar. `useToolbarItem()` inside it
+  says where the item sits.
+-->
+<script lang="ts">
+  import { untrack } from 'svelte';
+  import { provideToolbarItem } from './item-context.svelte.js';
+  import type { ToolbarItemProps } from './props.js';
+
+  let { id, children }: ToolbarItemProps = $props();
+
+  const place = provideToolbarItem();
+  let element: HTMLDivElement | undefined = $state();
+  $effect(() => {
+    const target = element;
+    if (!target) return;
+    // Reading the attributes writes the context, which this effect must not depend on.
+    return untrack(() => place.follow(target));
+  });
+
+  // Spread, `slot` is the element's attribute: written out, Svelte reads it as a slot of its own.
+  const slot = $derived({ slot: `item:${id}` });
+</script>
+
+<div bind:this={element} {...slot} style="display: contents">{@render children?.()}</div>

package/dist/slots/ToolbarItem.svelte.d.ts

@@ -0,0 +1,4 @@
+import type { ToolbarItemProps } from './props.js';
+declare const ToolbarItem: import("svelte").Component<ToolbarItemProps, {}, "">;
+type ToolbarItem = ReturnType<typeof ToolbarItem>;
+export default ToolbarItem;

package/dist/slots/item-context.svelte.d.ts

@@ -0,0 +1,27 @@
+/**
+ * Where a toolbar item sits, as the viewer tells it. The viewer keeps that on the item's element as
+ * `data-orientation`, `data-edge`, `data-variant` and `data-size`; `ToolbarItem` reads them, live,
+ * into a reactive object for `useToolbarItem()`. A change reaches your component in the microtasks
+ * after the viewer writes it, before the browser lays the bar out, so the toolbar measures your
+ * component in the variant it picked.
+ */
+import type { ToolbarItemContext, ToolbarItemEdge, ViewerSize } from '@embedpdf/viewer/core';
+/** An item's context as a reactive object: each field reads the latest the viewer wrote. */
+export declare class ToolbarItemPlace implements ToolbarItemContext {
+    #private;
+    get orientation(): ToolbarItemContext['orientation'];
+    get edge(): ToolbarItemEdge;
+    get variant(): string | null;
+    get size(): ViewerSize;
+    /** Read what the viewer says on `element`, now and whenever it writes it. Returns the stop. */
+    follow(element: Element): () => void;
+}
+/** For `ToolbarItem`: the context of the item it makes, for the components inside it. */
+export declare function provideToolbarItem(): ToolbarItemPlace;
+/**
+ * Where the toolbar item this component is in sits, as a reactive object: which way its bar runs
+ * (`orientation`), the bar's place (`edge`), which of the item's `variants` the toolbar picked
+ * (`variant`), and the viewer's size (`size`). Read the fields where you use them
+ * (`item.orientation`), so they stay live. Works inside a `ToolbarItem`.
+ */
+export declare function useToolbarItem(): ToolbarItemContext;

package/dist/slots/item-context.svelte.js

@@ -0,0 +1,73 @@
+import { getContext, hasContext, setContext } from 'svelte';
+const EDGES = ['top', 'bottom', 'start', 'end', 'float', 'selection'];
+const SIZES = ['compact', 'medium', 'expanded'];
+/** Before the viewer says where the item is: the main bar's place. */
+const AT_THE_TOP = {
+    orientation: 'horizontal',
+    edge: 'top',
+    variant: null,
+    size: 'expanded',
+};
+const ATTRIBUTES = ['data-orientation', 'data-edge', 'data-variant', 'data-size'];
+/** Where the item whose element is `element` sits, as the viewer wrote it there. */
+function toolbarItemContextOf(element) {
+    const edge = element.getAttribute('data-edge');
+    const size = element.getAttribute('data-size');
+    return {
+        orientation: element.getAttribute('data-orientation') === 'vertical' ? 'vertical' : 'horizontal',
+        edge: edge && EDGES.includes(edge) ? edge : AT_THE_TOP.edge,
+        variant: element.getAttribute('data-variant'),
+        size: size && SIZES.includes(size) ? size : AT_THE_TOP.size,
+    };
+}
+const sameContext = (left, right) => left.orientation === right.orientation &&
+    left.edge === right.edge &&
+    left.variant === right.variant &&
+    left.size === right.size;
+/** An item's context as a reactive object: each field reads the latest the viewer wrote. */
+export class ToolbarItemPlace {
+    #current = $state.raw(AT_THE_TOP);
+    get orientation() {
+        return this.#current.orientation;
+    }
+    get edge() {
+        return this.#current.edge;
+    }
+    get variant() {
+        return this.#current.variant;
+    }
+    get size() {
+        return this.#current.size;
+    }
+    /** Read what the viewer says on `element`, now and whenever it writes it. Returns the stop. */
+    follow(element) {
+        const read = () => {
+            const next = toolbarItemContextOf(element);
+            if (!sameContext(this.#current, next))
+                this.#current = next;
+        };
+        read();
+        const observer = new MutationObserver(read);
+        observer.observe(element, { attributes: true, attributeFilter: ATTRIBUTES });
+        return () => observer.disconnect();
+    }
+}
+const TOOLBAR_ITEM = Symbol('embedpdf.toolbar-item');
+/** For `ToolbarItem`: the context of the item it makes, for the components inside it. */
+export function provideToolbarItem() {
+    const place = new ToolbarItemPlace();
+    setContext(TOOLBAR_ITEM, place);
+    return place;
+}
+/**
+ * Where the toolbar item this component is in sits, as a reactive object: which way its bar runs
+ * (`orientation`), the bar's place (`edge`), which of the item's `variants` the toolbar picked
+ * (`variant`), and the viewer's size (`size`). Read the fields where you use them
+ * (`item.orientation`), so they stay live. Works inside a `ToolbarItem`.
+ */
+export function useToolbarItem() {
+    if (!hasContext(TOOLBAR_ITEM)) {
+        throw new Error('[embedpdf] useToolbarItem() works inside a <ToolbarItem>: it says where that item sits.');
+    }
+    return getContext(TOOLBAR_ITEM);
+}

package/dist/slots/props.d.ts

@@ -0,0 +1,22 @@
+/** The props of your own components' places in the viewer: `ToolbarItem`, `Panel`, `Region`. */
+import type { Snippet } from 'svelte';
+export interface ToolbarItemProps {
+    /** The item's id: `{ custom: id }` in the layout. */
+    id: string;
+    children?: Snippet;
+}
+export interface PanelProps {
+    /** The panel's id, as `addPanel(id, …)` names it in the layout. */
+    id: string;
+    children?: Snippet;
+}
+/**
+ * A place around the viewer for your own components: `header` above everything, `footer` below
+ * everything, `tabs` in place of the document tabs, `empty` over the pages while no document is
+ * open.
+ */
+export type RegionName = 'header' | 'footer' | 'tabs' | 'empty';
+export interface RegionProps {
+    name: RegionName;
+    children?: Snippet;
+}

package/dist/slots/props.js

@@ -0,0 +1 @@
+export {};

package/dist/slots.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Your own components in the viewer: `ToolbarItem`, `Panel` and `Region` put your component in
+ * the place the viewer makes for it (`item:<id>`, `panel:<id>`, or a region's name). It renders as
+ * a child of the `<embedpdf-viewer>` element, so it stays in your Svelte tree, with your context,
+ * your state and your CSS; the browser shows it in that place. `useToolbarItem()` tells a
+ * component inside a `ToolbarItem` where it sits.
+ */
+export { default as ToolbarItem } from './slots/ToolbarItem.svelte';
+export { default as Panel } from './slots/Panel.svelte';
+export { default as Region } from './slots/Region.svelte';
+export { useToolbarItem } from './slots/item-context.svelte.js';
+export type { PanelProps, RegionName, RegionProps, ToolbarItemProps } from './slots/props.js';

package/dist/slots.js

@@ -0,0 +1,11 @@
+/**
+ * Your own components in the viewer: `ToolbarItem`, `Panel` and `Region` put your component in
+ * the place the viewer makes for it (`item:<id>`, `panel:<id>`, or a region's name). It renders as
+ * a child of the `<embedpdf-viewer>` element, so it stays in your Svelte tree, with your context,
+ * your state and your CSS; the browser shows it in that place. `useToolbarItem()` tells a
+ * component inside a `ToolbarItem` where it sits.
+ */
+export { default as ToolbarItem } from './slots/ToolbarItem.svelte';
+export { default as Panel } from './slots/Panel.svelte';
+export { default as Region } from './slots/Region.svelte';
+export { useToolbarItem } from './slots/item-context.svelte.js';

package/dist/viewer-components/Button.svelte

@@ -0,0 +1,22 @@
+<!--
+  A toolbar button, the viewer's own: `<epdf-button>`, which the viewer draws like the buttons in
+  its bars. `command` makes it that command's button; or give it an `icon`, a `label` and an
+  `onclick`. Use it inside the viewer: in a `ToolbarItem`, a `Panel` or a `Region`.
+-->
+<script lang="ts">
+  import type { ButtonProps } from './props.js';
+
+  let { command, icon, label, onclick, class: className, style }: ButtonProps = $props();
+</script>
+
+<!-- What's left out is null: the element writes its properties to attributes, `undefined` too.
+     It draws a real button in its own shadow root, which takes the keys and fires the click. -->
+<!-- svelte-ignore a11y_click_events_have_key_events, a11y_no_static_element_interactions -->
+<epdf-button
+  command={command ?? null}
+  icon={icon ?? null}
+  label={label ?? null}
+  {onclick}
+  class={className}
+  {style}
+></epdf-button>

package/dist/viewer-components/Button.svelte.d.ts

@@ -0,0 +1,4 @@
+import type { ButtonProps } from './props.js';
+declare const Button: import("svelte").Component<ButtonProps, {}, "">;
+type Button = ReturnType<typeof Button>;
+export default Button;

package/dist/viewer-components/Menu.svelte

@@ -0,0 +1,13 @@
+<!--
+  A button that opens a menu of `MenuItem`s, the viewer's own `<epdf-menu>`: it opens the way the
+  viewer's menus do, away from its bar, flipped when there's no room, and up from the bottom on a
+  phone.
+-->
+<script lang="ts">
+  import type { MenuProps } from './props.js';
+
+  let { icon, label, children }: MenuProps = $props();
+</script>
+
+<!-- What's left out is null: the element writes its properties to attributes, `undefined` too. -->
+<epdf-menu icon={icon ?? null} {label}>{@render children?.()}</epdf-menu>

package/dist/viewer-components/Menu.svelte.d.ts

@@ -0,0 +1,4 @@
+import type { MenuProps } from './props.js';
+declare const Menu: import("svelte").Component<MenuProps, {}, "">;
+type Menu = ReturnType<typeof Menu>;
+export default Menu;

package/dist/viewer-components/MenuItem.svelte

@@ -0,0 +1,15 @@
+<!--
+  A row in a `Menu`, the viewer's own `<epdf-menu-item>`: its text is the row's. `command` makes it
+  that command's row; picking it runs the command, and calls `onselect` either way (the element's
+  `select` event).
+-->
+<script lang="ts">
+  import type { MenuItemProps } from './props.js';
+
+  let { command, icon, onselect, children }: MenuItemProps = $props();
+</script>
+
+<!-- What's left out is null: the element writes its properties to attributes, `undefined` too. -->
+<epdf-menu-item command={command ?? null} icon={icon ?? null} {onselect}
+  >{@render children?.()}</epdf-menu-item
+>

package/dist/viewer-components/MenuItem.svelte.d.ts

@@ -0,0 +1,4 @@
+import type { MenuItemProps } from './props.js';
+declare const MenuItem: import("svelte").Component<MenuItemProps, {}, "">;
+type MenuItem = ReturnType<typeof MenuItem>;
+export default MenuItem;

package/dist/viewer-components/props.d.ts

@@ -0,0 +1,31 @@
+/** The props of the viewer's own components for yours: `Button`, `Menu` and `MenuItem`. */
+import type { Snippet } from 'svelte';
+export interface ButtonProps {
+    /** Makes it this command's button: its icon, tooltip and state, and it runs it. */
+    command?: string;
+    /** An icon by name, the viewer's or yours, for a button of your own. */
+    icon?: string;
+    /** The name of a button of your own, for its tooltip and screen readers. */
+    label?: string;
+    onclick?: (event: MouseEvent) => void;
+    class?: string;
+    style?: string;
+}
+export interface MenuProps {
+    /** The icon of the button that opens it, by name. */
+    icon?: string;
+    /** Its name, for the button's tooltip and screen readers. */
+    label: string;
+    /** Its rows: `MenuItem`s. */
+    children?: Snippet;
+}
+export interface MenuItemProps {
+    /** Makes it this command's row: its icon, label and state, and picking it runs it. */
+    command?: string;
+    /** An icon by name, the viewer's or yours. */
+    icon?: string;
+    /** Called when the row is picked. */
+    onselect?: () => void;
+    /** Its text. */
+    children?: Snippet;
+}

package/dist/viewer-components/props.js

@@ -0,0 +1 @@
+export {};

package/dist/viewer-components.d.ts

@@ -0,0 +1,10 @@
+/**
+ * The viewer's own components, for yours: `Button`, `Menu` and `MenuItem` render the viewer's
+ * `<epdf-button>`, `<epdf-menu>` and `<epdf-menu-item>` elements, which the viewer draws like its
+ * own toolbar buttons and menus. Use them inside the viewer: in a `ToolbarItem`, a `Panel` or a
+ * `Region`. The elements come with the viewer, so these import nothing from it.
+ */
+export { default as Button } from './viewer-components/Button.svelte';
+export { default as Menu } from './viewer-components/Menu.svelte';
+export { default as MenuItem } from './viewer-components/MenuItem.svelte';
+export type { ButtonProps, MenuItemProps, MenuProps } from './viewer-components/props.js';

package/dist/viewer-components.js

@@ -0,0 +1,9 @@
+/**
+ * The viewer's own components, for yours: `Button`, `Menu` and `MenuItem` render the viewer's
+ * `<epdf-button>`, `<epdf-menu>` and `<epdf-menu-item>` elements, which the viewer draws like its
+ * own toolbar buttons and menus. Use them inside the viewer: in a `ToolbarItem`, a `Panel` or a
+ * `Region`. The elements come with the viewer, so these import nothing from it.
+ */
+export { default as Button } from './viewer-components/Button.svelte';
+export { default as Menu } from './viewer-components/Menu.svelte';
+export { default as MenuItem } from './viewer-components/MenuItem.svelte';

package/package.json

@@ -1,6 +1,70 @@
 {
   "name": "@embedpdf/viewer-svelte",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
+  "version": "3.0.0-next.16",
+  "private": false,
+  "description": "Svelte wrapper for the full viewer: the PDFViewer component around the embedpdf-viewer custom element. Your own components (ToolbarItem, Panel, Region) are light-DOM children the viewer shows in its slots while they stay in your Svelte tree (your context, your CSS). The viewer inside is the Preact-compiled artifact.",
+  "type": "module",
+  "types": "./dist/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "svelte": "./dist/index.js",
+      "default": "./dist/index.js"
+    },
+    "./core": {
+      "types": "./dist/core.d.ts",
+      "svelte": "./dist/core.js",
+      "default": "./dist/core.js"
+    },
+    "./component": {
+      "types": "./dist/parts.d.ts",
+      "svelte": "./dist/parts.js",
+      "default": "./dist/parts.js"
+    },
+    "./package.json": "./package.json"
+  },
+  "files": [
+    "dist"
+  ],
+  "dependencies": {
+    "esm-env": "^1.2.2",
+    "@embedpdf/viewer": "3.0.0-next.16",
+    "@embedpdf/svelte": "3.0.0-next.16"
+  },
+  "peerDependencies": {
+    "svelte": "^5.29.0"
+  },
+  "devDependencies": {
+    "@sveltejs/package": "^2.5.0",
+    "@sveltejs/vite-plugin-svelte": "^6.0.0",
+    "@types/node": "^22.0.0",
+    "playwright-core": "^1.63.0",
+    "svelte": "^5.39.5",
+    "svelte-check": "^4.3.0",
+    "typescript": "~5.8.3",
+    "vite": "^6.3.5",
+    "vitest": "^2.1.9",
+    "@embedpdf/tooling-build": "0.0.0"
+  },
+  "license": "Apache-2.0",
+  "sideEffects": [
+    "./src/index.ts",
+    "./src/core.ts",
+    "./dist/index.js",
+    "./dist/core.js"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/embedpdf/embed-pdf-viewer.git",
+    "directory": "packages/viewer/svelte"
+  },
+  "scripts": {
+    "build": "svelte-package --input src --output dist && node ../../../tooling/build/src/fully-specify-imports.mjs && node ../../../tooling/build/src/check-framework-package.mjs",
+    "clean": "rimraf dist",
+    "typecheck": "svelte-check --tsconfig ./tsconfig.json --threshold error && svelte-check --tsconfig ./test/tsconfig.json --threshold error",
+    "test": "vitest run"
+  }
 }