Skip to content

feat(svelte): @seamless-auth/svelte bindings #172

Closed

Description

@Bccorb

Part of fells-code/seamless-auth-api#371.

Bindings for Svelte on top of the framework-agnostic @seamless-auth/client, matching what @seamless-auth/react offers.

Activity

  1. Bccorb commented on Oct 9, 2026

    @Bccorb
    ContributorAuthor

    Done. @seamless-auth/svelte 0.1.0 is published from #181 and Version Packages #182. The browser project landed in fells-code/seamless-cli#260, and its verify / verify check passed in CI. That check runs the React browser specs (register, email OTP, magic link, passkey register and login, OAuth, logout) against a SvelteKit 3 reference app, on both its production build and vite dev. A local released-mode run against the published packages also passed all 13 layers.

    • Session state and auth actions, exposed idiomatically: createSeamlessAuth returns a session whose properties are runes, shared through setSeamlessAuth and getSeamlessAuth
    • Login, passkey registration and OAuth callback views, plus headless use and styling guidance (package README)
    • Route guards: requireAuth and requireGuest load functions for SvelteKit 2.26 and later, and SvelteKit 3, in @seamless-auth/svelte/kit
    • Nothing Svelte-specific in @seamless-auth/client. The screens reuse the shared flows and the stylesheet in resources/styles, and they navigate through an AuthNavigator, so routers other than SvelteKit can drive them
    • Browser project in the verify harness (feat(verify): run the browser specs against a SvelteKit app seamless-cli#260)

    A security review ran before the release. Its fixes shipped with it: dropQuery is a real replace navigation, so the magic link token and OAuth code leave SvelteKit's URL state and history; the guards run again when the session changes; and a destination outside the base path falls back to signedInPath.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions