Jesse Pence (@JessePence5) header
Jesse Pence (@JessePence5) profile picture

JavaScript Framework Nerd

Vancouver, WA
Joined February 2020
Photo by Jesse Pence (@JessePence5)Photo by Jesse Pence (@JessePence5)Photo by Jesse Pence (@JessePence5)Photo by Jesse Pence (@JessePence5)Photo by Jesse Pence (@JessePence5)Photo by Jesse Pence (@JessePence5)Photo by Jesse Pence (@JessePence5)Photo by Jesse Pence (@JessePence5)Photo by Jesse Pence (@JessePence5)Photo by Jesse Pence (@JessePence5)
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/…
21
126
8
719
114,802
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…
1
8
23
3,840
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?
6
2
18
2,894
👀
5
6
102
14,216
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 👇
2
7
1
16
3,498
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. 👊💥🦆
32
24
8
281
57,321
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…
4
17
6
135
19,132
Jesse Pence retweeted
In the currently released version of Chrome: chrome://flags/#observable-api
13
16
12
122
15,306
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!
1
66
16,443
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!
2
2
29
2,803
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!
16
37
10
481
96,720
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.
6
9
76
17,540
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 …
8
75
11
771
113,504
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
2
3
16
2,052
Jesse Pence retweeted
Want to read the entire code of Zustand v5-alpha? Here you go!
Zustand v4.5.0 is released! Docs for the new feature are work in progress. I also published the first alpha version for v5. Please try it and report what you find. v5 doesn't add any new features, just drops some, and becomes much smaller.
17
74
15
927
168,948
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!
13
23
1
256
60,232
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…
3
7
1
61
12,984
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…
6
29
2
196
17,744
Jesse Pence retweeted
What's!?
12
20
6
269
32,788
Jesse Pence retweeted
Let me simplify it
5
12
5
272
44,296