You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 requireGuestload 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
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.
Activity
feat(svelte): add @seamless-auth/svelte bindings (#181)
Bccorb commentedon Oct 9, 2026
Done.
@seamless-auth/svelte0.1.0 is published from #181 and Version Packages #182. The browser project landed in fells-code/seamless-cli#260, and itsverify / verifycheck 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 andvite dev. A local released-mode run against the published packages also passed all 13 layers.createSeamlessAuthreturns a session whose properties are runes, shared throughsetSeamlessAuthandgetSeamlessAuthrequireAuthandrequireGuestloadfunctions for SvelteKit 2.26 and later, and SvelteKit 3, in@seamless-auth/svelte/kit@seamless-auth/client. The screens reuse the sharedflowsand the stylesheet inresources/styles, and they navigate through anAuthNavigator, so routers other than SvelteKit can drive themA security review ran before the release. Its fixes shipped with it:
dropQueryis 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 tosignedInPath.