jwt-auth VS jetstream

First, thank you to everyone who contributed to Tymon's JWT Auth library. I found there were various issues with it (lasagna code, having to extend/override existing functionality, lack of functionality, etc.) that made it challenging to work with, which is what inspired me to create Little JWT.

Due to inactivity by the maintainer, this has forced laravel developers that use php 8, to look for alternatives. Here is a list of alternatives to the tymondesigns/jwt-auth package, that i have managed to find, in my quest to find alternative packages.

I'm not sure if Sanctum is fine for generating tokens because the jwt-auth package seems to be abandoned. For context, I'm used to develop with Laravel plain html, and now I want to separate front-end with Svelte and back-end with Laravel, as because I'm used to it. The questions is: Is it ok to just use Sanctum package? I know it's not really jwt token, but seems to do the job.

Jwt-auth

You can make a login route in api.php and then return the token if you want simpler token for authentication might I suggest that you use jwt token it's simple and it's docs show you how to use the jwt token https://github.com/tymondesigns/jwt-auth if you want something complex then sanctum can help you for example you can give token different abilities if you want to create an auth token use auth()->user()->createToken(); To create a token

You can use spatie roles and permissions. This package for jwt is good: https://github.com/tymondesigns/jwt-auth

tymon/jwt-auth: https://github.com/tymondesigns/jwt-auth tymon/jwt-auth document: https://jwt-auth.readthedocs.io/en/develop/

jwt-auth provides a simple means of authentication within Laravel using JSON Web Tokens. JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.

I used Laravel Jetstream to kickstart a few things for me, such as Authentication, Teams, and API support.

For writing models I would suggest using Action Closes. One example of them can be found in Jetstream's sourcecode. Actions are great to test in isolation and link to user stories.

While I prefer python for everything else, I'd go with Laravel Jetstream[1] for an MVP, just like I did with the last one I had to build. It's laravel, you can use Vue (React or Svelte) for your views instead of the blade templating language that comes with the framework. Jetstream also comes with Auth, user login and subscription and other useful stuff.

And for the flavor, I'd just go with DaisyUI[2] again, since it's based on tailwindcss and it's what I've been using lately.

In my experience, I can build MVPs real fast with the stack described above.

[1] https://jetstream.laravel.com

A well-implemented example of this would be in Laravel Jetstream, where an Actions namespace is defined for performing user-oriented tasks in Laravel Fortify — such as updating the user profile.

This legacy package is a very simple authentication scaffolding built on the Bootstrap CSS framework. While it continues to work with the latest version of Laravel, you should consider using Laravel Breeze for new projects. Or, for something more robust, consider Laravel Jetstream.

Laravel provide us with robust solutions and starter kits for authentication so let's start by creating a new Laravel 9 project and install Jetstram