Pinned Tweet
So, in order to explain RSC's, I wanted to give some background about the development of JavaScript promises, streams, workers, etc.
With each concept, I kept finding myself jumping back and forth through time. So, I decided to start at the beginning.
jessedit.tech/articles/react…
2
9
2,624
Jesse Pence retweeted
A lot of smart folks have been working on this proposal to bring native signals to JavaScript.
…Also I’ve been helping the smart people.
Have a look.
github.com/proposal-signals/…
Jesse Pence retweeted
Today let's learn about four key primitives in @solid_js (signals, createAsync, server functions, and actions) brenelz.com/posts/learning-f…
Jesse Pence retweeted
This is a typical vinxi config for a SSRed Solid app. solid-start's actual config is not very far from this.
I just want to get a sense of how much of this makes sense intuitively. Feedback?
Jesse Pence retweeted
Here's a new demo of Custom States that works in all browsers.
Chrome, Edge, Safari Tech Preview with CustomStateSet feature flag and Firefox 122 with dom.element.customstateset.enabled set to true.
Codepen link 👇
Jesse Pence retweeted
A concise example of why I really don't like decorators that much.
IMO, decorators should have been metadata only. We already have enough ways to duck-punch JavaScript into oblivion. 👊💥🦆
Jesse Pence retweeted
Ever wonder about how we got here? Tomorrow's stream I'm going to look at what's been going on the past several years in front-end web dev, and what that means for the future.
youtube.com/live/aA7Xeh7WG4E…
Jesse Pence retweeted
In the currently released version of Chrome:
chrome://flags/#observable-api
Jesse Pence retweeted
This is very important, so 👀. I’ve believed for a while that commoditizing end to end the setup, bundling utilities, low level primitives and consumption of RSCs is required for them succeed and actually grow beyond one of two routers on a single framework running on canaries.
Made some progress on supporting React Server Components in Parcel over the weekend. Will be very different from other implementations:
• Not a framework. No router, server, networking layer, cache, etc. — just the raw bundling primitives.
• Use with any server/router (eg express). Instead of an HTML file, your server JS file is the entry point. In each route, dynamic import a server component and render it to HTML or RSC payload. Client components and styles used by that server component are optimally bundled and loaded automatically.
• You can fetch a server component whenever you want, with any networking layer. Doesn’t need to be on a route boundary (eg infinite scroll), can be sent via a web socket if you want, etc.
My hope is that by exposing the raw primitives, it’ll be easier to see how RSC works and enable more freedom to experiment. Parcel is particularly well suited for this because it already supports multi-target module graphs with a single entry point. Will share more soon!
Jesse Pence retweeted
YES PLEASE
RSCs have a very strong future if they can be used and adopted with much more minimal and customizable setups
Which means commoditize bundling and generalize routing
Can’t wait for Parcel, Vinxi, Turbopack, and hopefully Bun to make RSCs a first class citizen
Made some progress on supporting React Server Components in Parcel over the weekend. Will be very different from other implementations:
• Not a framework. No router, server, networking layer, cache, etc. — just the raw bundling primitives.
• Use with any server/router (eg express). Instead of an HTML file, your server JS file is the entry point. In each route, dynamic import a server component and render it to HTML or RSC payload. Client components and styles used by that server component are optimally bundled and loaded automatically.
• You can fetch a server component whenever you want, with any networking layer. Doesn’t need to be on a route boundary (eg infinite scroll), can be sent via a web socket if you want, etc.
My hope is that by exposing the raw primitives, it’ll be easier to see how RSC works and enable more freedom to experiment. Parcel is particularly well suited for this because it already supports multi-target module graphs with a single entry point. Will share more soon!
Jesse Pence retweeted
Made some progress on supporting React Server Components in Parcel over the weekend. Will be very different from other implementations:
• Not a framework. No router, server, networking layer, cache, etc. — just the raw bundling primitives.
• Use with any server/router (eg express). Instead of an HTML file, your server JS file is the entry point. In each route, dynamic import a server component and render it to HTML or RSC payload. Client components and styles used by that server component are optimally bundled and loaded automatically.
• You can fetch a server component whenever you want, with any networking layer. Doesn’t need to be on a route boundary (eg infinite scroll), can be sent via a web socket if you want, etc.
My hope is that by exposing the raw primitives, it’ll be easier to see how RSC works and enable more freedom to experiment. Parcel is particularly well suited for this because it already supports multi-target module graphs with a single entry point. Will share more soon!
Jesse Pence retweeted
I wonder when people will start talking about the difference between loading data in Server Components and Client Components. There are many benefits to using SCs to load data but it comes with tradeoffs. Having optimal SC fetching doesn't necessarily excuse poor CC fetching.
Jesse Pence retweeted
I built a thing last week: it’s a Scroll-Driven View Transition.
Yep, you read that right: the View Transition is controlled by you scrolling! There’s a lot to tell about this one, so let’s take a look …
Jesse Pence retweeted
there’s no denying that ai is changing how we work and’s finding its way into many of our workflows. that being said, there are things I WON’T use it for
new video up now (link in next tweet) – at Portland, OR
Jesse Pence retweeted
Want to read the entire code of Zustand v5-alpha? Here you go!
Jesse Pence retweeted
Form validation is hard. Especially with all the server stuff React is doing.
Here's a guide to help you do forms right!
Jesse Pence retweeted
Today's stream I'm going to continue the conversation on HTML partials and the complexity of state and view coordination across the server/client boundary.
youtube.com/live/N-QwFFqI8aQ…
Jesse Pence retweeted
Ever wonder what makes Signals special or the difference in reactive systems?
It often lies in how state is derived.
"Derivations in Reactivity" by @RyanCarniato #webdev #javascript #reactivity #signals dev.to/this-is-learning/deri…
Jesse Pence retweeted
Let me simplify it

ALT Meme with two vertical panels. each panel shows a person walking left to right on a sidewalk in 4 steps, each step having text above it. The top panel is titled "SPA before" and the text is 1) bundle app.js and upload bundle to CDN. 2) client sends an HTTP request 3) cdn responds with HTML + js 4) client displays HTML + js. The bottom panel is titled RSC SPA and the text is 1) render app.js and upload bundle to CDN 2) client sends an HTTP request 3) cdn responds with HTML+js 4) client displays HTML + js
























