jetstream
jwt-auth
Our great sponsors
jetstream | jwt-auth | |
---|---|---|
23 | 10 | |
3,881 | 11,153 | |
0.9% | - | |
8.7 | 4.4 | |
7 days ago | 25 days ago | |
PHP | PHP | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
jetstream
-
Ask HN: What would be your stack if you are building an MVP today?
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.
- Admin panel with basic html css js
-
`npm run dev` not copying css or js files to public. Bug?
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.
-
Controllers vs livewire components
Jetstream is not a bad place to start: https://github.com/laravel/jetstream/tree/2.x/src
- Jetstream - Allow personal teams to be optional
-
How Laravel Livewire works (a deep dive)
I get your point and this conversation might be as old as Laravel itself. I would like to point out a couple of things though:
The "hop in and be productive" part is directly related to Laravel being pretty opinionated. It's hard to have the one without the other. I think it's comparable to Steve Jobs, who had pretty strong opinions about certain things, too. The end result is a "product" that doesn't try to be the right fit for everyone.
Livewire, just like Jetstream[1] etc. is opt-in. When Jetstream was introduced, there was quite an uproar (by parts of the community) about Laravel forcing users into Livewire or Inertia[2]. The end result was (imho) a very healthy shift in communication around it (to emphasize the opt-in part), followed by the introduction of Breeze[3], which goes to show that Taylor does recognize the reservations some people may have about those new shiny toys.
It's a very natural thing that big projects like that will have an ever-growing feature set. That is an important part of keeping existing users excited. The Jetstream-discussion has been an important lesson for the team (I hope) and I'm glad it ended the way it did.
You can still build your Laravel app in a pretty similar fashion as you would have done 5 years ago and if you want, you can make use of the recent additions, so I think there's not too much to worry about to be honest. If you have outgrown the magic, isn't it pretty amazing that you can drop down one level of abstraction and just use symfony? Also, do you think you would've grasped many of the underlying features of symfony, if it wasn't for Laravel's opinionated wrapping in a nicer syntax (pardon my oversimplification)?
Nevertheless, I think it's good to keep up the warning signs and have this discussion from time to time. ;-)
-
Jetstream dropped support for translation/localization (?!)
The commit, the issue
They have good reasons to drop it, read the whole discussion under that commit, because it seems you didn't as those problems were discussed there.
-
Livewire Notifier
Make sure that Livewire and Alpine.JS are installed properly. The easiest way to do it is to install Laravel Jetstream with Livewire stack (post-install command php artisan jetstream:install livewire).
-
Implementing Laravel's built-in token authentication
More often than not when developing an application you're going to need some mechanism of authentication. Up until recently, Laravel shipped with a complete authentication toolbox: controllers, routes and views. Recently Laravel migrated a lot of its backend authentication functionality into Laravel Fortify and provided a frontend simple implementation using Breeze. There's also a more opinionated auth setup using JetStream which combines Fortify and other currently-popular frontend tools Livewire and (my personal favorite) Inertiajs.
jwt-auth
-
Generate and verify JSON Web Tokens simply with Little JWT
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.
-
Rants on PHP8.1
So lucky you! I am so stuck with tymon/jwt-auth and even changed to php-open-source-saver/jwt-auth and they haven't fully compatible with 8.1 yet :(
-
Alternatives 🔥😊 to the abandoned tymondesigns / jwt-auth 😠 laravel auth package
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.
-
Best Open Source Laravel Projects On GitHub
Jwt-auth
-
Laravel + Inertia (Vue JS) - how to handle API tokens?
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
-
Most Useful GitHub repositories for Laravel
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.
What are some alternatives?
breeze - Minimal Laravel authentication scaffolding with Blade, Vue, or React + Tailwind.
django-unicorn - The magical reactive component framework for Django ✨
jwt-auth - 🔐 JSON Web Token Authentication for Laravel & Lumen
Tailwind CSS - A utility-first CSS framework for rapid UI development.
livewire - A full-stack framework for Laravel that takes the pain out of building dynamic UIs.
Voyager - Voyager - The Missing Laravel Admin
crudbooster - Laravel CRUD Generator, Make an Advanced Web Application Quickly
sanctum - Laravel Sanctum provides a featherweight authentication system for SPAs and simple APIs.
laravel-filemanager - Media gallery with CKEditor, TinyMCE and Summernote support. Built on Laravel file system.
materio-vuetify-vuejs-laravel-admin-template-free - Production Ready, Carefully Crafted, Extensive Vuejs Laravel Free Admin Template 🤩
Vue.js - This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core