next-react-server-components
Blitz
next-react-server-components | Blitz | |
---|---|---|
6 | 23 | |
962 | 13,390 | |
0.2% | 0.3% | |
6.1 | 8.7 | |
6 months ago | 16 days ago | |
JavaScript | TypeScript | |
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.
next-react-server-components
-
Having a hard time getting into Next with 12/13
There is a number of public, easy-to-understand projects you can check out after you've digested all the new patterns from the docs (and maybe that tutorial): https://github.com/shadcn/next-contentlayer https://github.com/vercel/next-react-server-components
- Next.js 13 + React Server Components
- Do you know a good tutorial on how to implement React Server Components? (For Side Project)
-
What's the difference between SSR Streaming and React Server Components?
In the official Next.js demo both approaches are mixed together. But aren't these different approaches?
-
Why are SSR Streaming and React Server Components presented together in one demo?
In the Next.js demo, SSR Streaming and React Server Components are presented together within one demo. Aren't the two approaches two different technologies that can be used independently?
-
Show HN: Hacker News Clone Using Remix and React
For comparison this[1] is Next.js implementation that uses React Server Components (RSC). I feel folks at Remix missed on React Server Components and now it will be a lot of work to make it work in Remix. Hopefully I'm wrong.
If you don't know, RSC allows the HTML from server to start streaming as React is rendering the components in the backend. It allows fine grain control to what part of page renders first and which parts can be rendered later as HTML and data is streaming from the server. Before this, all of React server frameworks would render the entire page, shove "hydration data" in it which is mostly repeated data that is used to render the page and also include that HTML in the form of complied JSX in the page in the page scripts. Obviously that would make React SSR very bulky and unscalable. That's why RSC can solve so many React performance problems
[1] https://github.com/vercel/next-react-server-components
Blitz
-
refine vs Blitz.js
Blitz is also an open-source project that allows users to access the code and allows to contribute. Their community has generated a lot of impact as well, and has grown rapidly over time since the creation in 2020:
-
Show HN: A social network like Myspace, built on top of Notion
Not yet, I actually just whipped it up quickly last week after I was browsing the Notion subreddit and it reminded me of myspace.
These are the tools I used:
* BlitzJS (https://github.com/blitz-js/blitz)
-
We built an open-source React-based framework(2.9k stars on GitHub) for building CRUD apps rapidly.
Maybe you could help/join this project? https://github.com/blitz-js/blitz
-
Blitz.js – The Missing Fullstack Toolkit for Next.js
Hello, I'm the creator of Blitz.js (first announced 2.5 years ago)
Today the Blitz.js 2.0 pivot to a modular Next.js toolkit reached Beta status [1]
Previously Blitz abstracted Next.js, but Blitz 2.0 is now a modular toolkit that plugs into any new or existing Next.js app. Blitz picks up where Next.js leaves off, providing libraries and conventions for shipping and scaling small to large apps.
When I first created Blitz, my aim was to have an all-in-one fullstack framework for Javascript like Ruby on Rails. But that proved to be too difficult. I've decided that achieving an all-in-one framework for JS like Rails is too difficult unless you have a ton of funding and don't have to make meaningful money.
The difference with JS is that client-side frameworks like React have an incredible amount of complexity. Trying to manage all of that and all the other fullstack framework stuff like API layers, auth, file uploads, etc is too large of scope.
So now Blitz is no longer trying to do it all and is focusing on all the non-frontend functionality you need to ship web apps.
Going forward, we want to be the most trusted technical resource for rapidly building and scaling full-stack TypeScript apps.
[1] https://github.com/blitz-js/blitz/releases/tag/v2.0.0-beta.1
- Blitz - ⚡️The Fullstack React Framework — built on Next.js
- NEXT is cool, is Blitz cooler?
- What handles Next better than Remix?
- What is your opinion on blitz.js and prisma? Do you think they could be used as an industry standard?
- Important Discussion on Possible Blitz.js Pivot