SaaSHub helps you find the best software and product alternatives Learn more →
Jetstream Alternatives
Similar projects and alternatives to jetstream
-
breeze
Minimal Laravel authentication scaffolding with Blade, Vue, or React + Tailwind. (by laravel)
-
-
InfluxDB
Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.
-
-
-
crudbooster
Laravel CRUD Generator, Make an Advanced Web Application Quickly
-
-
Vue.js
This is the repo for Vue 2. For Vue 3, go to https://github.com/vuejs/core
-
SonarLint
Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.
-
-
livewire-notifier
Simple notifications system with zero dependencies above TALL-stack.
-
Alpine.js
A rugged, minimal framework for composing JavaScript behavior in your markup.
-
-
-
-
-
laravel-filemanager
Media gallery with CKEditor, TinyMCE and Summernote support. Built on Laravel file system.
-
-
Nest
A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications on top of TypeScript & JavaScript (ES6, ES7, ES8) 🚀
-
-
Hasura
Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
jetstream reviews and mentions
-
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.
-
A note from our sponsor - #<SponsorshipServiceOld:0x00007f160cfd2428>
www.saashub.com | 30 Mar 2023
Stats
laravel/jetstream is an open source project licensed under MIT License which is an OSI approved license.