Alex Sidorenko
@asidorenko_
Followers
34K
Following
13K
Media
942
Statuses
4K
In Next.js (with cacheComponents), awaiting runtime data (like "params") defines the static/dynamic boundary of your page Move awaits closer to where they're needed
8
31
365
Those enforce the Rules of React (previously eslint-plugin-react-compiler, now merged to eslint-plugin-react-hooks) https://t.co/9SXxLf4DT0
react.dev
The library for web and native user interfaces
0
0
16
"How can I prepare my Next.js app for React compiler?" Next 16 contains additional ESlint rules for that
6
15
236
And it does so using <Activity />, which is really interesting https://t.co/JmPpNNqvvv
nextjs.org
Learn how to use Cache Components and combine the benefits of static and dynamic rendering.
1
2
66
Next.js preserves client state on the page during navigation when cacheComponents is enabled
63
116
2K
"ai doesn't know Next 16 and cacheComponents" Try Next.js mcp
18
42
934
Today, we’re officially releasing React Native Godot to the public. For the first time, every React Native developer can create games with an amazing UI on top. This unlocks a new era of apps and games. https://t.co/FD2kpOKcoB
240
919
9K
My previous suggestion was to use loading.tsx, but with cacheComponents enabled, the actual part of your page outside of Suspense boundaries acts like loading.tsx (static, prefetched) I'm not sure if you need loading.tsx with cacheComponents at all https://t.co/GueCROrHSX
"Navigation feels slow in Next.js" Use loading.tsx instead of Suspense when possible
1
2
50
"Navigation feels slow in Next.js" Try cacheComponents 👇
61
84
2K
I'm too dumb to understand how Remix 3 will compare to React in practice (without actually trying it), but it's exciting to see someone trying a different model It benefits everyone in the community either way. Competition breeds excellence P.S. Ryan is a very good presenter
Hey, I know you think this.update() is manual updates but setState for some reason isn't (?) there's something more interesting. Did you see that frame.reload() reconciled AN HTML RESPONSE against both the REAL DOM and the HYDRATED COMPONENTS?!
2
2
105
Setting a cookie in server action automatically re-renders the current page and its layouts in Next.js
16
25
518
There is more to cacheComponents, of course. I will create a few more vids But it seems to fix the accidental dynamic rendering problem which is huge. Rendering strategy and caching gets much more explicit https://t.co/SuKWT0S7V1
The most annoying part of Next.js, by far, is how easy you can make a route dynamically rendered by accident. Even when you use `generateStaticParams`, you would think it would be, well, static. But sneaky usage of headers(), cookies(), etc... will make it SSR.
0
1
26