Create a JWT authentication system instead of clerk (third party authentication)

[prateekydv01]

Hi sir

I’d like to contribute by replacing the current Clerk-based authentication with a custom JWT-based system.

Why:

• Avoid vendor lock-in and dependency on third-party auth
• Enable full control over auth flow, token contents, and security
• Improve flexibility for self-hosting or custom deployments

What I’m proposing:

• Implement custom auth with JWTs (login/register/logout routes)
• Replace Clerk UI with custom forms and context
• Add route protection using JWT middleware
• Document the new setup clearly in the README

Would you be open to this kind of contribution? If yes, I’ll be happy to work on a PR.

Looking forward to your thoughts 🙌

[ashwith123]

Hi! 👋

I’d love to take up this issue and implement the migration from Clerk to a custom JWT-based authentication system as described.

I’ve worked with JWT auth flows before and can handle:

• Setting up secure login/register/logout routes
• Creating and verifying JWTs (access & refresh tokens if needed)
• Protecting routes with middleware
• Replacing Clerk UI with clean custom forms
• Updating the README with setup instructions

Let me know if this is open for contribution — happy to start right away!