@andco/sdk-svelte 0.0.1

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Andco
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://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.

package/README.md

@@ -0,0 +1,168 @@
+# `@andco/sdk-svelte`
+
+Svelte 5 bindings for `@andco/sdk`, implemented with runes, callback props,
+and Svelte context.
+
+Svelte creates and owns the iframe. The package does not wrap a Web Component or
+delegate rendering to a shared DOM function.
+
+## Install
+
+```sh
+pnpm add @andco/sdk-svelte svelte
+```
+
+## Configure a subtree
+
+`AndcoProvider` either builds the Andco Instance for you from `clientOptions`, or takes an
+instance you already own via `client` (useful when the application builds it with
+`createAndcoInstanceForBrowser` from `@andco/sdk/browser` itself, or on a server-rendered app
+that wants to hand the provider a session resolved ahead of time via `initialSession`):
+
+```svelte
+<script lang="ts">
+  import { AndcoProvider } from "@andco/sdk-svelte";
+
+  import App from "./App.svelte";
+
+  const clientOptions = {
+    clientId: "client_123",
+    endpointAuth: "https://auth.example.com",
+    endpointApi: "https://api.example.com",
+    endpointWidget: "https://widgets.example.com",
+    redirectTo: "https://app.example.com/auth/callback",
+    initialScopes: ["openid", "email", "profile"],
+    locale: "es-CL",
+  };
+</script>
+
+<AndcoProvider {clientOptions}>
+  <App />
+</AndcoProvider>
+```
+
+`clientOptions` is the same `AndcoBrowserOptions` shape `createAndcoInstanceForBrowser` takes
+(everything `AndcoClientOptions` accepts, minus the server-only `presenter`/`source`/`clientSecret`
+fields), so `allowedPopupOrigins`, `apiVersion`, `theme`, `themeMode`, `detectSessionInUrl`, and the
+rest of that type belong here too when needed — there is no separate function or component prop for
+them.
+
+## Hosted sign-in
+
+Svelte 5 callback props use lowercase DOM-style names. `AndcoButton` takes its client, endpoints,
+and theme from the `<AndcoProvider>` context, not from props — the only thing a per-render sign-in
+needs to pass is `authorization`, the same request-local options `auth.signIn` accepts (`scopes`,
+`redirectTo`, `orgId`, `authorizationDetails`, `resource`, …):
+
+```svelte
+<script lang="ts">
+  import { AndcoButton } from "@andco/sdk-svelte";
+  let message = $state<string>();
+</script>
+
+<AndcoButton
+  authorization={{ scopes: ["openid", "email", "profile"] }}
+  oncomplete={() => console.log("Authorized")}
+  onerror={(error) => (message = error.message)}
+/>
+```
+
+Available callbacks are `onready`, `onactivate`, `oncomplete`, `ondismiss`, and `onerror`. There is
+no `onstatechange` — read `useAndcoSession()` instead if a component needs to react to every state
+change, including a silent token rotation.
+
+## Reactive session
+
+```svelte
+<script lang="ts">
+  import { useAndco, useAndcoSession, useAndcoUser } from "@andco/sdk-svelte";
+
+  const andco = useAndco();
+  const session = useAndcoSession();
+  const user = useAndcoUser();
+</script>
+
+{#if user.current}
+  <p>Signed in as {user.current.name ?? user.current.email}</p>
+  <button type="button" onclick={() => void andco.current.auth.signOut()}>Sign out</button>
+{/if}
+```
+
+Every hook returns `{ readonly current }` rather than a raw value, because a
+rune's reactivity does not survive being returned by value — read `.current`
+directly from markup and derived runes.
+
+`useAndco().current` is `AndcoClient | AndcoClientAuthed` and changes
+reference exactly when the Authorized Identity does — sign-in, sign-out, a
+widened Grant — and stays the same reference across a token rotation, which is
+why an `$effect` reading `andco.current` re-runs on a sign-in but not on a
+silent refresh. `useAndcoAuthed().current` is the same change rule narrowed to
+`AndcoClientAuthed | null`, for the "do this once signed in" path.
+
+`useAndcoSession().current` changes on *every* republication, rotations
+included — reach for it when you need the credential as data, such as an
+expiry, or to observe the unresolved-to-anonymous transition `useAndco`
+deliberately hides. `useAndcoUser().current` changes only when the person
+changes — identifier, name, email, or avatar.
+
+## Progressive scopes
+
+```svelte
+{#if session.current && !session.current.scopes.includes("bank_accounts:read")}
+  <AndcoButton authorization={{ scopes: ["openid", "email", "profile", "bank_accounts:read"] }} />
+{/if}
+```
+
+## Intents
+
+`andco.intents` is domain-neutral: it only knows how to create, read, execute, and observe an
+Intent generically, regardless of the domain that Intent belongs to. Bind it to the signed-in
+identity once, then use it directly:
+
+```svelte
+<script lang="ts">
+  import { useAndcoAuthed } from "@andco/sdk-svelte";
+
+  const andco = useAndcoAuthed();
+</script>
+```
+
+```svelte
+<script lang="ts">
+  async function topUp() {
+    if (!andco.current) return;
+    const { data: intent, error } = await andco.current.intents.create(
+      "deposit",
+      {
+        expires_in: "30 minutes",
+        amount: { currency: "CLP", suggested: "40000", editable: false },
+        note: { suggested: "Wallet top-up", editable: true },
+        metadata: { merchant_transaction_id: "deposit_8472" },
+      },
+      { idempotencyKey: "deposit:8472" },
+    );
+    if (error) throw error;
+  }
+</script>
+
+<button type="button" onclick={() => void topUp()}>Top up</button>
+```
+
+`AndcoIntentButton` renders the same hosted iframe as `AndcoButton`, with its `flow` fixed to
+`"intent"` — the Hosted Intent Presentation is the canonical way a person confirms an Intent, and
+its DOM and code stay Andco's, never the Project's. It takes the same props as `AndcoButton`
+(`authorization`, `busy`, `disabled`, `locale`, `release`, `themeMode`, and the `onready` /
+`onactivate` / `oncomplete` / `ondismiss` / `onerror` callbacks); there is currently no prop to
+target a specific, already-created Intent, and `oncomplete` takes no arguments — read the Intent's
+state with `andco.current.intents.get(intentId)` after it fires, or through
+`andco.current.intents.events(intentId)` / `andco.current.intents.subscribe(...)`, rather than
+expecting it on the callback.
+
+```svelte
+<AndcoIntentButton onerror={(error) => console.error(error.message)} />
+```
+
+See [`apps/example-svelte`](../../apps/example-svelte/README.md) for the complete
+session → Grant → resource flow.
+
+There is no separate hosted-vs-direct pair of Intent buttons — `AndcoIntentButton` is the only one.

package/dist/AndCoButton.svelte

@@ -0,0 +1,97 @@
+<script lang="ts">
+  import type { AndcoError } from "@andco/sdk";
+  import {
+    AndcoButtonController,
+    type AndcoButtonControllerOptions,
+    type AndcoButtonSnapshot,
+  } from "@andco/sdk/browser";
+  import type { HTMLIframeAttributes } from "svelte/elements";
+  import { andcoContext } from "./context.svelte.js";
+
+  type Options = AndcoButtonControllerOptions;
+  type Props = Omit<HTMLIframeAttributes, "onerror" | "referrerpolicy" | "sandbox" | "src" | "srcdoc"> &
+    Pick<Options, "authorization" | "busy" | "disabled" | "flow" | "locale" | "release" | "themeMode"> & {
+      onready?: Options["onReady"];
+      onactivate?: Options["onActivate"];
+      oncomplete?: () => void;
+      ondismiss?: () => void;
+      onerror?: (error: AndcoError) => void;
+    };
+
+  let {
+    authorization,
+    busy,
+    disabled,
+    flow,
+    locale,
+    release,
+    themeMode,
+    onready,
+    onactivate,
+    oncomplete,
+    ondismiss,
+    onerror,
+    title = "Andco",
+    ...attributes
+  }: Props = $props();
+
+  // The stable instance, read directly off the context rather than through `useAndco`: the bridge
+  // controller must not be rebuilt on sign-in.
+  const client = andcoContext().client;
+  let iframe = $state<HTMLIFrameElement>();
+  let snapshot = $state<AndcoButtonSnapshot>();
+  let controller = $state<AndcoButtonController>();
+
+  $effect(() => {
+    const next = new AndcoButtonController({
+      client,
+      ...(authorization ? { authorization } : {}),
+      ...(flow ? { flow } : {}),
+      ...(release === undefined ? {} : { release }),
+      ...(themeMode ? { themeMode } : {}),
+      ...(locale ? { locale } : {}),
+      ...(disabled === undefined ? {} : { disabled }),
+      ...(busy === undefined ? {} : { busy }),
+      onReady: (event) => onready?.(event),
+      onActivate: (event) => onactivate?.(event),
+      onComplete: () => oncomplete?.(),
+      onDismiss: () => ondismiss?.(),
+      onError: (error) => onerror?.(error),
+    });
+    controller = next;
+    const stop = next.subscribe((value) => {
+      snapshot = value;
+    });
+    return () => {
+      stop();
+      next.destroy();
+      controller = undefined;
+    };
+  });
+
+  // The controller's returned disconnect is the effect's cleanup, which is the whole reason every
+  // subscription in this SDK answers with a plain function.
+  //
+  // It depends on the element and the controller only. Reading the snapshot here would close a
+  // cycle, because connecting publishes a new snapshot; the bridge already re-runs its handshake on
+  // the iframe's own `load`, so a URL change needs no reconnection from here.
+  $effect(() => {
+    if (!iframe || !controller) return;
+    return controller.connect(iframe);
+  });
+</script>
+
+<!--
+  A bare iframe is 300x150 with a border, and the hosted control fills whatever box it is given, so
+  without a default the application sees a bordered grey slab. A `style` on the component wins.
+-->
+<iframe
+  style="border:0;display:block;height:3rem;width:18rem"
+  {...attributes}
+  bind:this={iframe}
+  hidden={!snapshot?.ready}
+  referrerpolicy="no-referrer"
+  sandbox="allow-scripts allow-same-origin allow-popups allow-popups-to-escape-sandbox"
+  src={snapshot?.iframeURL}
+  {title}
+></iframe>

package/dist/AndCoButton.svelte.d.ts

@@ -0,0 +1,14 @@
+import type { AndcoError } from "@andco/sdk";
+import { type AndcoButtonControllerOptions } from "@andco/sdk/browser";
+import type { HTMLIframeAttributes } from "svelte/elements";
+type Options = AndcoButtonControllerOptions;
+type Props = Omit<HTMLIframeAttributes, "onerror" | "referrerpolicy" | "sandbox" | "src" | "srcdoc"> & Pick<Options, "authorization" | "busy" | "disabled" | "flow" | "locale" | "release" | "themeMode"> & {
+    onready?: Options["onReady"];
+    onactivate?: Options["onActivate"];
+    oncomplete?: () => void;
+    ondismiss?: () => void;
+    onerror?: (error: AndcoError) => void;
+};
+declare const AndCoButton: import("svelte").Component<Props, {}, "">;
+type AndCoButton = ReturnType<typeof AndCoButton>;
+export default AndCoButton;

package/dist/AndCoIntentButton.svelte

@@ -0,0 +1,9 @@
+<script lang="ts">
+  import AndcoButton from "./AndCoButton.svelte";
+
+  // The same hosted control in its Intent flow, not a parallel implementation. Two implementations
+  // of one presentation is what let the previous direct and hosted paths drift apart.
+  let props = $props();
+</script>
+
+<AndcoButton {...props} flow="intent" />

package/dist/AndCoIntentButton.svelte.d.ts

@@ -0,0 +1,3 @@
+declare const AndCoIntentButton: import("svelte").Component<$$ComponentProps, {}, "">;
+type AndCoIntentButton = ReturnType<typeof AndCoIntentButton>;
+export default AndCoIntentButton;

package/dist/AndCoProvider.svelte

@@ -0,0 +1,51 @@
+<script lang="ts">
+  import type { AndcoClient, AndcoSession } from "@andco/sdk";
+  import { type AndcoBrowserOptions, createAndcoInstanceForBrowser } from "@andco/sdk/browser";
+  import type { Snippet } from "svelte";
+  import { setAndcoContext } from "./context.svelte.js";
+
+  type Props = {
+    children: Snippet;
+    clientOptions?: AndcoBrowserOptions;
+    /** An instance the application already owns. Wins when both are given. */
+    client?: AndcoClient;
+    /** A session the server already resolved, so the first frame is real rather than unresolved. */
+    initialSession?: AndcoSession | null;
+  };
+
+  let { children, client, clientOptions, initialSession }: Props = $props();
+
+  // svelte-ignore state_referenced_locally
+  //
+  // Capturing the initial values is the intent. An Andco Instance is a value identified by its
+  // configuration, and its store may already be loading; rebuilding it because a prop changed
+  // would throw that away and, on a callback page, discard a single-use authorization code. An
+  // application that genuinely needs a different configuration mounts a different provider.
+  if (!client && !clientOptions) throw new Error("AndcoProvider requires either clientOptions or client");
+
+  // svelte-ignore state_referenced_locally
+  const instance =
+    client ??
+    createAndcoInstanceForBrowser({
+      ...(clientOptions as AndcoBrowserOptions),
+      ...(initialSession === undefined ? {} : { initialSession }),
+    });
+
+  let session = $state<AndcoSession | null | undefined>(instance.session.getSnapshot());
+
+  // Subscribing is what starts the load, and the returned function is the cleanup.
+  $effect(() =>
+    instance.session.subscribe(() => {
+      session = instance.session.getSnapshot();
+    }),
+  );
+
+  setAndcoContext({
+    client: instance,
+    get session() {
+      return session;
+    },
+  });
+</script>
+
+{@render children()}

package/dist/AndCoProvider.svelte.d.ts

@@ -0,0 +1,14 @@
+import type { AndcoClient, AndcoSession } from "@andco/sdk";
+import { type AndcoBrowserOptions } from "@andco/sdk/browser";
+import type { Snippet } from "svelte";
+type Props = {
+    children: Snippet;
+    clientOptions?: AndcoBrowserOptions;
+    /** An instance the application already owns. Wins when both are given. */
+    client?: AndcoClient;
+    /** A session the server already resolved, so the first frame is real rather than unresolved. */
+    initialSession?: AndcoSession | null;
+};
+declare const AndCoProvider: import("svelte").Component<Props, {}, "">;
+type AndCoProvider = ReturnType<typeof AndCoProvider>;
+export default AndCoProvider;

package/dist/context.svelte.d.ts

@@ -0,0 +1,84 @@
+import { type AndcoClient, type AndcoClientAuthed, type AndcoSession, type AndcoUser } from "@andco/sdk";
+export type AndcoSvelteContext = {
+    /** The instance. One reference for the provider's lifetime — never `with(...)` or `authorized()`. */
+    readonly client: AndcoClient;
+    readonly session: AndcoSession | null | undefined;
+};
+export declare function setAndcoContext(context: AndcoSvelteContext): void;
+/**
+ * The raw context: the stable instance plus the raw session.
+ *
+ * Not exported from the package. It exists for components inside this package — {@link AndCoButton}
+ * in particular — that need the stable instance without going through {@link useAndco}, which hands
+ * out a new reference on sign-in and would rebuild the bridge for no reason.
+ */
+export declare function andcoContext(): AndcoSvelteContext;
+/**
+ * Reads the Andco Instance, as a value that changes when the Authorized Identity does.
+ *
+ * Start here. The instance carries the methods and resolves the token, so this is what an
+ * `$effect` or a `$derived` is usually written against, and reading it does what it reads like:
+ * the effect re-runs on sign-in, on sign-out, and when granted scopes change. It does *not* re-run
+ * on a token rotation, which changes no answer this instance would give.
+ *
+ * While there is no Authorized Identity — the session is unresolved or anonymous — `current` is the
+ * instance itself, `isAuthed === false`, and that reference is stable across the
+ * unresolved-to-anonymous transition. An effect that must react to *that* transition reads
+ * {@link useAndcoSession} instead, since `useAndco` deliberately does not change reference for it.
+ *
+ * Behind a getter, because a rune's reactivity does not survive being returned by value. See
+ * {@link useAndcoAuthed} for the same change rule narrowed to `null` while signed out, and
+ * {@link useAndcoUser} for the person alone.
+ *
+ * @example
+ * ```svelte
+ * const andco = useAndco();
+ * $effect(() => { void andco.current; loadAccounts(); });
+ * ```
+ */
+export declare function useAndco(): {
+    readonly current: AndcoClient | AndcoClientAuthed;
+};
+/**
+ * Reads the authorized arm of the Andco Instance, or `null` while there is no Authorized Identity.
+ *
+ * Same change rule as {@link useAndco}: a new reference on sign-in, on sign-out, and on a widened
+ * Grant, and the same reference across a token rotation. Reach for this instead of `useAndco` when
+ * the common "do this once signed in" path should need no guard beyond a null check — `current` is
+ * `null` for both the unresolved and the anonymous session, so the distinction between them is not
+ * observable here; read {@link useAndcoSession} when it matters.
+ *
+ * @example
+ * ```svelte
+ * const andco = useAndcoAuthed();
+ * $effect(() => {
+ *   if (andco.current) loadAccounts(andco.current);
+ * });
+ * ```
+ */
+export declare function useAndcoAuthed(): {
+    readonly current: AndcoClientAuthed | null;
+};
+/**
+ * The current session, as three distinct states.
+ *
+ * `undefined` means the store has not finished loading; `null` means signed out. Rendering them the
+ * same way flashes a signed-out state on every load. Unlike {@link useAndco}, this changes on
+ * *every* republication — including a silent token rotation — because whoever reads it is reading
+ * the credential as data, not asking whether the Authorized Identity changed.
+ *
+ * Returned behind a getter because a rune's reactivity does not survive being returned by value.
+ */
+export declare function useAndcoSession(): {
+    readonly current: AndcoSession | null | undefined;
+};
+/**
+ * The authenticated person, or `null`/`undefined` sharing {@link useAndcoSession}'s three states.
+ *
+ * Changes reference only when the person changes — identifier, name, email, or avatar — never on a
+ * token rotation and never on a widened Grant, so an effect keyed on it does not reload a profile
+ * for a change the person did not make. See {@link useAndco} for the client itself.
+ */
+export declare function useAndcoUser(): {
+    readonly current: AndcoUser | null | undefined;
+};

package/dist/context.svelte.js

@@ -0,0 +1,143 @@
+import { sessionIdentityKey, } from "@andco/sdk";
+import { createContext } from "svelte";
+const [get, set] = createContext();
+export function setAndcoContext(context) {
+    set(context);
+}
+/**
+ * The raw context: the stable instance plus the raw session.
+ *
+ * Not exported from the package. It exists for components inside this package — {@link AndCoButton}
+ * in particular — that need the stable instance without going through {@link useAndco}, which hands
+ * out a new reference on sign-in and would rebuild the bridge for no reason.
+ */
+export function andcoContext() {
+    try {
+        return get();
+    }
+    catch {
+        throw new Error("useAndco requires an <AndcoProvider> above it");
+    }
+}
+/**
+ * Reads the Andco Instance, as a value that changes when the Authorized Identity does.
+ *
+ * Start here. The instance carries the methods and resolves the token, so this is what an
+ * `$effect` or a `$derived` is usually written against, and reading it does what it reads like:
+ * the effect re-runs on sign-in, on sign-out, and when granted scopes change. It does *not* re-run
+ * on a token rotation, which changes no answer this instance would give.
+ *
+ * While there is no Authorized Identity — the session is unresolved or anonymous — `current` is the
+ * instance itself, `isAuthed === false`, and that reference is stable across the
+ * unresolved-to-anonymous transition. An effect that must react to *that* transition reads
+ * {@link useAndcoSession} instead, since `useAndco` deliberately does not change reference for it.
+ *
+ * Behind a getter, because a rune's reactivity does not survive being returned by value. See
+ * {@link useAndcoAuthed} for the same change rule narrowed to `null` while signed out, and
+ * {@link useAndcoUser} for the person alone.
+ *
+ * @example
+ * ```svelte
+ * const andco = useAndco();
+ * $effect(() => { void andco.current; loadAccounts(); });
+ * ```
+ */
+export function useAndco() {
+    const value = andcoContext();
+    // `$derived` rather than a manually cached getter: Svelte only re-notifies a dependent `$effect`
+    // when a derived's *value* changes, so computing the identity as its own derived and the view as
+    // a derived over that is what makes a rotation — same identity string, new session object — a
+    // no-op for anything reading `current`, instead of merely returning a stable reference to an
+    // effect that already reran.
+    const identity = $derived(sessionIdentityKey(value.session));
+    const view = $derived.by(() => identity === "unresolved" || identity === "anonymous" ? value.client : value.client.authorized());
+    return {
+        get current() {
+            return view;
+        },
+    };
+}
+/**
+ * Reads the authorized arm of the Andco Instance, or `null` while there is no Authorized Identity.
+ *
+ * Same change rule as {@link useAndco}: a new reference on sign-in, on sign-out, and on a widened
+ * Grant, and the same reference across a token rotation. Reach for this instead of `useAndco` when
+ * the common "do this once signed in" path should need no guard beyond a null check — `current` is
+ * `null` for both the unresolved and the anonymous session, so the distinction between them is not
+ * observable here; read {@link useAndcoSession} when it matters.
+ *
+ * @example
+ * ```svelte
+ * const andco = useAndcoAuthed();
+ * $effect(() => {
+ *   if (andco.current) loadAccounts(andco.current);
+ * });
+ * ```
+ */
+export function useAndcoAuthed() {
+    const value = andcoContext();
+    const identity = $derived(sessionIdentityKey(value.session));
+    const view = $derived.by(() => identity === "unresolved" || identity === "anonymous" ? null : value.client.authorized());
+    return {
+        get current() {
+            return view;
+        },
+    };
+}
+/**
+ * The current session, as three distinct states.
+ *
+ * `undefined` means the store has not finished loading; `null` means signed out. Rendering them the
+ * same way flashes a signed-out state on every load. Unlike {@link useAndco}, this changes on
+ * *every* republication — including a silent token rotation — because whoever reads it is reading
+ * the credential as data, not asking whether the Authorized Identity changed.
+ *
+ * Returned behind a getter because a rune's reactivity does not survive being returned by value.
+ */
+export function useAndcoSession() {
+    const value = andcoContext();
+    return {
+        get current() {
+            return value.session;
+        },
+    };
+}
+/**
+ * The authenticated person, or `null`/`undefined` sharing {@link useAndcoSession}'s three states.
+ *
+ * Changes reference only when the person changes — identifier, name, email, or avatar — never on a
+ * token rotation and never on a widened Grant, so an effect keyed on it does not reload a profile
+ * for a change the person did not make. See {@link useAndco} for the client itself.
+ */
+export function useAndcoUser() {
+    const value = andcoContext();
+    let cached;
+    // `$derived.by` for the same reason as `useAndco`: recomputing on every session read is fine, but
+    // handing back `cached` unchanged is what stops a dependent `$effect` from re-running on a
+    // rotation, since Svelte compares the derived's produced value, not what was read to produce it.
+    const user = $derived.by(() => {
+        const session = value.session;
+        if (session === undefined) {
+            cached = undefined;
+            return cached;
+        }
+        if (session === null) {
+            cached = null;
+            return cached;
+        }
+        const next = session.user;
+        if (!cached ||
+            cached.id !== next.id ||
+            cached.name !== next.name ||
+            cached.email !== next.email ||
+            cached.avatarUrl !== next.avatarUrl) {
+            cached = next;
+        }
+        return cached;
+    });
+    return {
+        get current() {
+            return user;
+        },
+    };
+}

package/dist/index.d.ts

@@ -0,0 +1,4 @@
+export { default as AndcoButton } from "./AndCoButton.svelte";
+export { default as AndcoIntentButton } from "./AndCoIntentButton.svelte";
+export { default as AndcoProvider } from "./AndCoProvider.svelte";
+export { type AndcoSvelteContext, setAndcoContext, useAndco, useAndcoAuthed, useAndcoSession, useAndcoUser, } from "./context.svelte.js";

package/dist/index.js

@@ -0,0 +1,4 @@
+export { default as AndcoButton } from "./AndCoButton.svelte";
+export { default as AndcoIntentButton } from "./AndCoIntentButton.svelte";
+export { default as AndcoProvider } from "./AndCoProvider.svelte";
+export { setAndcoContext, useAndco, useAndcoAuthed, useAndcoSession, useAndcoUser, } from "./context.svelte.js";

package/package.json

@@ -0,0 +1,47 @@
+{
+  "name": "@andco/sdk-svelte",
+  "version": "0.0.1",
+  "private": false,
+  "publishConfig": {
+    "access": "public"
+  },
+  "type": "module",
+  "sideEffects": false,
+  "svelte": "./dist/index.js",
+  "exports": {
+    ".": {
+      "types": "./dist/index.d.ts",
+      "svelte": "./dist/index.js",
+      "import": "./dist/index.js",
+      "default": "./dist/index.js"
+    }
+  },
+  "files": [
+    "dist"
+  ],
+  "peerDependencies": {
+    "svelte": "^5.0.0"
+  },
+  "dependencies": {
+    "@andco/sdk": "0.0.1"
+  },
+  "devDependencies": {
+    "@sveltejs/package": "^2.0.0",
+    "@sveltejs/vite-plugin-svelte": "^7.3.0",
+    "svelte": "^5.57.1",
+    "svelte-check": "^4.0.0",
+    "typescript": "^6.0.3",
+    "vite": "^8.3.0",
+    "vitest": "^5.0.1"
+  },
+  "license": "Apache-2.0",
+  "description": "Svelte bindings for the Andco SDK.",
+  "scripts": {
+    "clean": "node -e \"require('node:fs').rmSync('dist', { recursive: true, force: true })\"",
+    "build": "pnpm run clean && svelte-package",
+    "dev": "svelte-package --watch",
+    "check-types": "svelte-check --tsconfig ./tsconfig.json",
+    "lint": "svelte-check --tsconfig ./tsconfig.json",
+    "test": "vitest run"
+  }
+}