HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
laravel
jetstream
PHP2021–2022
laravel / jetstream

jetstream

Tailwind scaffolding for the Laravel framework.

2Distinct people
2Mentions
0Explicit recommenders
4.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Tailwind scaffolding for the Laravel framework.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2021-10-13 10:59:05 UTC to 2022-04-10 09:00:26 UTC. Weeks start Monday, UTC.

012021-10-11 00:00:00 UTC to 2021-10-18 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 112021-10-18 00:00:00 UTC to 2021-10-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-10-25 00:00:00 UTC to 2021-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-11-01 00:00:00 UTC to 2021-11-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-11-08 00:00:00 UTC to 2021-11-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-11-15 00:00:00 UTC to 2021-11-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-11-22 00:00:00 UTC to 2021-11-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-11-29 00:00:00 UTC to 2021-12-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-06 00:00:00 UTC to 2021-12-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-13 00:00:00 UTC to 2021-12-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-20 00:00:00 UTC to 2021-12-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2021-12-27 00:00:00 UTC to 2022-01-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-03 00:00:00 UTC to 2022-01-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 32022-01-10 00:00:00 UTC to 2022-01-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-17 00:00:00 UTC to 2022-01-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-24 00:00:00 UTC to 2022-01-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-31 00:00:00 UTC to 2022-02-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-02-07 00:00:00 UTC to 2022-02-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-02-14 00:00:00 UTC to 2022-02-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-02-21 00:00:00 UTC to 2022-02-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-02-28 00:00:00 UTC to 2022-03-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-03-07 00:00:00 UTC to 2022-03-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-03-14 00:00:00 UTC to 2022-03-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-03-21 00:00:00 UTC to 2022-03-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-03-28 00:00:00 UTC to 2022-04-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-04-04 00:00:00 UTC to 2022-04-11 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsApr 4

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 112021-10-11 00:00:00 UTC2021-10-18 00:00:00 UTC101
Oct 182021-10-18 00:00:00 UTC2021-10-25 00:00:00 UTC000
Oct 252021-10-25 00:00:00 UTC2021-11-01 00:00:00 UTC000
Nov 12021-11-01 00:00:00 UTC2021-11-08 00:00:00 UTC000
Nov 82021-11-08 00:00:00 UTC2021-11-15 00:00:00 UTC000
Nov 152021-11-15 00:00:00 UTC2021-11-22 00:00:00 UTC000
Nov 222021-11-22 00:00:00 UTC2021-11-29 00:00:00 UTC000
Nov 292021-11-29 00:00:00 UTC2021-12-06 00:00:00 UTC000
Dec 62021-12-06 00:00:00 UTC2021-12-13 00:00:00 UTC000
Dec 132021-12-13 00:00:00 UTC2021-12-20 00:00:00 UTC000
Dec 202021-12-20 00:00:00 UTC2021-12-27 00:00:00 UTC000
Dec 272021-12-27 00:00:00 UTC2022-01-03 00:00:00 UTC000
Jan 32022-01-03 00:00:00 UTC2022-01-10 00:00:00 UTC000
Jan 102022-01-10 00:00:00 UTC2022-01-17 00:00:00 UTC000
Jan 172022-01-17 00:00:00 UTC2022-01-24 00:00:00 UTC000
Jan 242022-01-24 00:00:00 UTC2022-01-31 00:00:00 UTC000
Jan 312022-01-31 00:00:00 UTC2022-02-07 00:00:00 UTC000
Feb 72022-02-07 00:00:00 UTC2022-02-14 00:00:00 UTC000
Feb 142022-02-14 00:00:00 UTC2022-02-21 00:00:00 UTC000
Feb 212022-02-21 00:00:00 UTC2022-02-28 00:00:00 UTC000
Feb 282022-02-28 00:00:00 UTC2022-03-07 00:00:00 UTC000
Mar 72022-03-07 00:00:00 UTC2022-03-14 00:00:00 UTC000
Mar 142022-03-14 00:00:00 UTC2022-03-21 00:00:00 UTC000
Mar 212022-03-21 00:00:00 UTC2022-03-28 00:00:00 UTC000
Mar 282022-03-28 00:00:00 UTC2022-04-04 00:00:00 UTC000
Apr 42022-04-04 00:00:00 UTC2022-04-11 00:00:00 UTC110

What Hacker News says

2 sources
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
Read the rest
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. ;-) [1] https://github.com/laravel/jetstream [2] https://inertiajs.com/ [3] https://github.com/laravel/breeze
In How Laravel Livewire works

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.