Server Components #2879
Replies: 4 comments 10 replies
-
|
Extracting static tress is something that's been on our mind for a while so we are very interested in that. The work in To quote Jason:
Rest assured that we'll keep pushing the boundaries for smaller sites and quicker boot up times. |
Beta Was this translation helpful? Give feedback.
-
|
Indeed. The result (HTML with islands of interactivity) is something we've already been executing around, but the specific technical approach React is using is not in line with Preact's goals. Preact aims to provide a platform-oriented take on VDOM, and as such we stick to using HTML to describe documents. It would certainly be possible to build out the wire protocol and client hydration similar to what they showed, and I'm sure folks will do this atop Preact as add-ons. For now though, we have other avenues to compiling applications to progressively-enhanced HTML that work with static hosting and prerendering too. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I ask me, why we go back to server? What about permanent data transfer and offline capability? |
Beta Was this translation helpful? Give feedback.
-
|
@deleonio My main take away from the react presentation was, the ability to offload heavy dependencies and computations to the server, so that that client only receives the rendered html to which you then can add interactivity again. Reduces bundle sizes and speeds up larger applications due to the partial hydration. If you need a heavy computation or certain dependency offline, you can still do that on the client. It just offers a way to ship less to clients ... |
Beta Was this translation helpful? Give feedback.
-
|
Partial hydration doesn't require server components, it requires server-side rendering or prerendering (which we already support). Offloading heavy computation to the server is anything but a new concept - folks doing API-first web application development have been doing this using REST/GraphQL/SOAP/etc for decades. There are numerous technical and nontechnical benefits to building an API for computationally expensive operations - many businesses have even monetized the APIs they developed for their own use as entire secondary product lines. |
Beta Was this translation helpful? Give feedback.
-
|
isn't it cool though, to have JSX used as a DSL for the server components. Elegant, more uniform code base for apps that use React. Also, the underlying streaming format should (could?) be more efficient than plain json/xml/etc. If the team/app is already locked in React, this could work nice for them... |
Beta Was this translation helpful? Give feedback.
-
|
@marvinhagemeister is the JSX plugin you made that compiles JSX to HTML still the favored approach? https://twitter.com/marvinhagemeist/status/1370041302935560194?s=21&t=80LTIJFd9Pq3eFROO6OKXA |
Beta Was this translation helpful? Give feedback.
-
|
Would be great to get an update here so Preact also allows async server-only components, now that
|
Beta Was this translation helpful? Give feedback.
-
|
Seems like there's some hints at movement on Preact Server Components from @marvinhagemeister over here: 
|
Beta Was this translation helpful? Give feedback.
-
|
Preact isn't abandoned, quite the opposite. Server components are already available in Fresh (=meta framework for Deno) since June 2022 and I'm currently exploring async server components on top of that (see: https://twitter.com/marvinhagemeist/status/1676535616563970048 ). Whilst server components are a no brainer, async ones are not as they have very real tradeoffs. V11 has been pushed back mostly because we managed to backport lots of the things into v10. I know that might not be as exciting as a splashy new major release, but it makes it much easier for bigger companies to adopt Preact. There are several ones of those moving to Preact in the recent months, which favour stability and ease of upgrading over everything else. All companies we cannot publicly talk about unless they share it on their terms, which is why there isn't much news around that. Then there is also the work in the ecosystem itself with Preact Signals being released not too long ago. All this work doesn't show up in this repository, but it's work that expands the Preact world and usage substantially. |
Beta Was this translation helpful? Give feedback.
-
|
I'm afraid features are going to be delivered to Fresh and take a long time to be pushed to Preact. I've seen you guys have been exploring with Async Server Components but seems there's no implementation of it outside of Fresh currently. I didn't know you guys were adding the v11 features into v10. That's really good to know and brings hope and I find it equally exciting actually. It's also good to know there's big companies "backing" Preact. Thanks for the friendly response! |
Beta Was this translation helpful? Give feedback.
-
Nah, that's not true. Just today I shipped support for error boundaries in preact-render-to-string because I need that for Fresh. Shipping that in There might be some more complex and more meta-framework-like features like async server components that will land in Fresh first. But that's actually a good thing because it allows us to find all the edge cases before upstreaming a more robust implementation to Preact itself. Then there is already another big feature planned for Preact apps that will ship soon that started its life as an exploration in Fresh. Preact users will be able to use that at the exact same time as Fresh users as the new feature isn't tied to Fresh at all. |
Beta Was this translation helpful? Give feedback.
-
|
Can we use Preact Async Components ? |
Beta Was this translation helpful? Give feedback.
-
This is going to be a bigger impact than Hooks were (IMO)
Professionally I adopted Preact on SSR'd sites for 3 core reasons:
I don't want to lose these by moving from Preact, but this announcement throws a spanner in the works as the examples are pretty mind-blowing.
What are everyone's thoughts here? I imagine this is FAR from a simple compat layer (given the intermediate format, streaming support etc)
Beta Was this translation helpful? Give feedback.
All reactions