Skip to content

Fix signin clientside sveltekit by adding /auth/ to the url #12846

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

printharsh
Copy link

@printharsh printharsh commented Apr 4, 2025

☕️ Reasoning

Fixes #12829. So on the sveltekit client when you do signin with a provider it properly uses the correct url /auth/signin and not /signin. Similarly for the signout routes from the client.

🧢 Checklist

  • Documentation
  • Tests
  • Ready to be merged

🎫 Affected issues

Fixes: #12829 And #12775

📌 Resources

@printharsh printharsh requested a review from ThangHuuVu as a code owner April 4, 2025 16:37
Copy link

vercel bot commented Apr 4, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
auth-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 4, 2025 4:41pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
next-auth-docs ⬜️ Ignored (Inspect) Visit Preview Apr 4, 2025 4:41pm

Copy link

vercel bot commented Apr 4, 2025

@printharsh is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

@Padi2312
Copy link

Padi2312 commented Apr 9, 2025

Can someone please approve this...

@stalkerg
Copy link

I can confirm, it's correct, and @balazsorban44 introduced the initial issue.

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

Successfully merging this pull request may close these issues.

SvelteKitError: Not found: /signin/google when using SvelteKit 5
3 participants