Repository navigation
docs(react): point the Next.js README section at @seamless-auth/nextjs - #183
Merged
Merged
Conversation
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.
Summary
The
@seamless-auth/reactREADME's Next.js section was stale. It said a dedicated Next.js server package was tracked in seamless-auth-server#170 and told readers to resolve the session withgetSeamlessUserfrom@seamless-auth/core.@seamless-auth/nextjshas shipped (0.4.0 on npm), so the section now points at it.packages/react/README.md: the Next.js section shows the install line, acreateSeamlessAuthHandlercatch-all route atapp/auth/[...seamless]/route.ts, and a root layout that resolves the session withgetSeamlessSessionand passes it toAuthProviderwithapiHost="". The pattern matches thetemplates/fullstack/nextjsstarter and the docs page, which is now linked (https://docs.seamlessauth.com/build/nextjs/). The server-side session paragraph now namesgetSeamlessSessionand keeps the warning against forwarding browser cookies to/auth/users/me. The link to seamless-auth-server#170 is gone.AGENTS.md: the Next.js notes said the server package "belongs in" seamless-auth-server and that server reads go throughgetSeamlessUser; they now say the package exists and Next.js reads go throughgetSeamlessSession.@seamless-auth/reactso the corrected README reaches npm.The other package READMEs (angular, vue, svelte, react-native, client) and the root README carry no stale Next.js claim. The Angular README's server-rendering note mentions
getSeamlessUseras an example for a generic server, which is still accurate.Checks
npm run format:check: passnpm run lint: passnpm run typecheck: passnpm test: 564 Jest tests and 39 Vitest tests pass