-
-
Notifications
You must be signed in to change notification settings - Fork 13
Feat/auth providers #46
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
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can I please get efficient screenshots and screen recording video to ensure that the primary behaviour won't break!
Thankyou
Screencast from 2025-10-03 17-29-06.zip ![]() ![]() |
A screen recording showing the current behaviour and ss pointing out the main changes have been attached A commit has been made removing the targeted emphasis on auth in the readme markdown as well |
Hey @saatvik-10, I want the auth providers to run with all setup done with the package, can u please confirm about the same? About the video: I want the video of the package running and the set-up for the auth providers running as expected than the tests running :) |
Any updates @saatvik-10 ? |
sry for the delay due to an emergency....will complete the requested by tomorrow in both the repos! |
@saatvik-10 take your time |
Description
Added authentication provider support to create-next-quick CLI tool. Users can now select from popular auth providers during project setup:
NextAuth.js
Clerk
Firebase Auth
None (default)
Related Issue
Fixes #20
Type of Change
Testing
Checklist
Screenshots