Vercel pricing update: CPU billing is now based on active usage, not function duration. This means you no longer pay for time spent waiting on external services such as databases, APIs, or LLMs. ↳ vercel.com/blog/introdu...
A great visual explanation by @delba.bsky.social (Be wary of Next.js 14 synchronous request APIs) www.youtube.com/watch?v=MTcP...
Next.js Visually Explained: Partial Pre-rendering (PPR)
YouTube video by Delba
youtube.com
Seeking a new role👍 If you hear of any opportunities/wanna catch up, DM/comment. 💼Looking for FE Dev(mid-level), Full Stack Dev (mid-level), DevRel(senior-level), & Docs Engineer(mid-senior) roles 🌎 Open to roles in remote & hybrid(🇩🇪) 🏆Experience: FE & Full Stack Dev(4 years) & DevRel(3.5 years)
🚀 @delba.bsky.social crushed it with an awesome talk on the future of UI development using React's #useClient directive, even though she couldn’t be with us in person! Check out how to optimize your web apps with better bundling and server-client harmony: hubs.li/Q02ZP3h20
Having poor performance with Partial Prerendering with @nextjs.org? Check your code if you're using revalidatePath. This is actually revalidating the entire static shell each time, making things really slow! Instead rely on router.refresh() to update your server component data.
If you use auth with refresh tokens that have automatic reuse detection. I.e. if an auth token is expired, you can request a new one using the refresh token only once. How do YOU on your site deal with the race condition where opening multiple tabs/requests at once logs the user out? Not at all?
My talk from #nextjsconf is now available on YouTube!
Optimizing LCP: Partial Prerendering deep dive (Wyatt Johnson)
YouTube video by Vercel
youtu.be
