Think I got my answer upstash.com/blog/fast-ne...
Somehow sounds unnatural to use a different router within Next, but hey if that works...
Somehow sounds unnatural to use a different router within Next, but hey if that works...
Making Next.js Navigation Fast af
Articles and tutorials on serverless technologies from Upstash and community
upstash.com
June 2, 2025 at 7:30 AM
Think I got my answer upstash.com/blog/fast-ne...
Somehow sounds unnatural to use a different router within Next, but hey if that works...
Somehow sounds unnatural to use a different router within Next, but hey if that works...
Like fetching RSC for html-heavy page makes sense, but sometimes I just want to not think about the server
May 12, 2025 at 6:40 PM
Like fetching RSC for html-heavy page makes sense, but sometimes I just want to not think about the server
Makes sense, but somehow easier for me to imagine the component taking the "use client" as the Boundary Client, and any component below it, including itself, as Client Components
Emphasizing this distinction between the component responsible of the boundary and other CC helps me a lot
Emphasizing this distinction between the component responsible of the boundary and other CC helps me a lot
May 12, 2025 at 5:06 PM
Makes sense, but somehow easier for me to imagine the component taking the "use client" as the Boundary Client, and any component below it, including itself, as Client Components
Emphasizing this distinction between the component responsible of the boundary and other CC helps me a lot
Emphasizing this distinction between the component responsible of the boundary and other CC helps me a lot
What do we think of actually naming the current "client component" into something more accurate like "boundary component"?
From my understanding that would make more sense and would have helped me shift my mental model muuch earlier
From my understanding that would make more sense and would have helped me shift my mental model muuch earlier
May 12, 2025 at 9:36 AM
What do we think of actually naming the current "client component" into something more accurate like "boundary component"?
From my understanding that would make more sense and would have helped me shift my mental model muuch earlier
From my understanding that would make more sense and would have helped me shift my mental model muuch earlier
Great article about promise serialization!
May 1, 2025 at 7:49 PM
Great article about promise serialization!