Reposted by ellemedit
the original mechanism was added here github.com/facebook/rea...
it effectively means that if SA receives some object and returns the same object within the response, it’s encoded as a reference (“argument number 3”) rather than serialized directly.
“use cache” memoization holes fall out of that
it effectively means that if SA receives some object and returns the same object within the response, it’s encoded as a reference (“argument number 3”) rather than serialized directly.
“use cache” memoization holes fall out of that
[Flight Reply] Encode Objects Returned to the Client by Reference by sebmarkbage · Pull Request #29010 · facebook/react
Stacked on #28997.
We can use the technique of referencing an object by its row + property name path for temporary references - like we do for deduping. That way we don't need to generate an ID...
github.com
May 2, 2025 at 10:06 AM
the original mechanism was added here github.com/facebook/rea...
it effectively means that if SA receives some object and returns the same object within the response, it’s encoded as a reference (“argument number 3”) rather than serialized directly.
“use cache” memoization holes fall out of that
it effectively means that if SA receives some object and returns the same object within the response, it’s encoded as a reference (“argument number 3”) rather than serialized directly.
“use cache” memoization holes fall out of that
Reposted by ellemedit
⚛️📝 New on Overreacted: JSX Over The Wire overreacted.io/jsx-over-the...
JSX Over The Wire — overreacted
Turning your API inside-out.
overreacted.io
April 15, 2025 at 3:54 PM
⚛️📝 New on Overreacted: JSX Over The Wire overreacted.io/jsx-over-the...
Reposted by ellemedit
You can pass sub-classed Promises to React such as in use() with the fields status and value or reason.
This allows React synchronously read the value without waiting on a microtask. This is much faster but it also ensures compat when someone needs flushSync().
Microtasks are bad, mkay.
This allows React synchronously read the value without waiting on a microtask. This is much faster but it also ensures compat when someone needs flushSync().
Microtasks are bad, mkay.
March 21, 2025 at 2:49 AM
You can pass sub-classed Promises to React such as in use() with the fields status and value or reason.
This allows React synchronously read the value without waiting on a microtask. This is much faster but it also ensures compat when someone needs flushSync().
Microtasks are bad, mkay.
This allows React synchronously read the value without waiting on a microtask. This is much faster but it also ensures compat when someone needs flushSync().
Microtasks are bad, mkay.
Reposted by ellemedit
I'm working on built-in profiling of both Client and Server Components in Chrome DevTools Performance tab. Thanks to the new performance.measure() extensions. h/t Andrés Olivares
This works in any RSC environment. In fact, this screenshot is running RSC for Parcel. h/t @devongovett.bsky.social
This works in any RSC environment. In fact, this screenshot is running RSC for Parcel. h/t @devongovett.bsky.social
December 12, 2024 at 4:25 AM
I'm working on built-in profiling of both Client and Server Components in Chrome DevTools Performance tab. Thanks to the new performance.measure() extensions. h/t Andrés Olivares
This works in any RSC environment. In fact, this screenshot is running RSC for Parcel. h/t @devongovett.bsky.social
This works in any RSC environment. In fact, this screenshot is running RSC for Parcel. h/t @devongovett.bsky.social
Reposted by ellemedit
I am once again begging everyone to read this article whenever core web vital comparisons are made web.dev/articles/vit...
How SPA architectures affect Core Web Vitals | Articles | web.dev
Answers to common questions about SPAs, Core Web Vitals, and Google's plan to address current measurement limitations.
web.dev
December 4, 2024 at 2:22 PM
I am once again begging everyone to read this article whenever core web vital comparisons are made web.dev/articles/vit...
I'm migrating all projects from legacy node.js, even Java Spring app to Next.js.
`use cache`, DataLoader combinations make stuff much easier to write and understand.
But there are still part has to be solved such as managing transaction scope or DTO/DAL/Repository layer thing.
`use cache`, DataLoader combinations make stuff much easier to write and understand.
But there are still part has to be solved such as managing transaction scope or DTO/DAL/Repository layer thing.
November 8, 2024 at 3:38 AM
I'm migrating all projects from legacy node.js, even Java Spring app to Next.js.
`use cache`, DataLoader combinations make stuff much easier to write and understand.
But there are still part has to be solved such as managing transaction scope or DTO/DAL/Repository layer thing.
`use cache`, DataLoader combinations make stuff much easier to write and understand.
But there are still part has to be solved such as managing transaction scope or DTO/DAL/Repository layer thing.