Repository navigation
Version Packages - #182
Merged
Merged
Version Packages#182
Conversation
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@seamless-auth/svelte@0.1.0
Minor Changes
d1a70a1: First release of
@seamless-auth/svelte, the Svelte binding for Seamless Auth (Svelte 5).createSeamlessAuth({ apiHost })creates a session whose properties (user,isAuthenticated,loading, and the rest) are runes, with every auth action.setSeamlessAuthandgetSeamlessAuthshare it through context.@seamless-auth/svelte/kitprovidesrequireAuth(auth, { roles })andrequireGuest(auth)loadguards, andcreateKitNavigatorfor the bundled screens, for SvelteKit 2.26 and later, and SvelteKit 3. Each guard waits for the session to be read.SaLogin,SaVerifyOtp,SaMagicLinkSent,SaVerifyMagicLink,SaOAuthCallback,SaPasskeyLogin,SaRegisterPasskey) to mount at your routes, themed with the same--seamless-*properties as the other bindings. They navigate through anAuthNavigator, so any router can drive them.The binding uses cookie transport only: tokens stay in the server adapter, and nothing is written where page scripts can read it.