I'm so tired of being expected to read things that no one has bothered to write.
I'm going on tour with the Next.js team in June! Coming to Amsterdam and London to share what's new in Next.js 16.3, hang out with the community, and answer your questions.
• June 9: San Francisco: luma.com/vercel-408x
• June 11: Amsterdam: luma.com/34nqdfc3
• June 18: London: luma.com/lfr946sc
Just ported my personal site over to @astro.build with a custom @bun.sh adapter I wrote 🚀
👋 I'm currently looking for my next role, so if you're hiring, reach out!
- Astro + Bun for blazing fast SSR
- Supports ISR and SWR
- Hosted behind @cloudflare.social
github.com/wyattjoh/ast...
Does this diagram help? It uses the React Performance Tracks to explain what React is doing, and what you'll see when you use the tracks:
github.com/reactjs/reac...
There are two ways to resolve the cognitive dissonance of being on Twitter while also caring about all the awful shit happening because of Twitter
1. Leave Twitter
2. Stop caring
Profoundly disappointing how many people I like seem to have chosen the latter
If you treat your default branch as something that went through PR review, you better make sure your workflow_dispatch doesn't do a checkout with a custom input.
Next.js is used by millions of developers across every major cloud. Making it work well everywhere is on us.
Here's what we've built with Netlify, Cloudflare, OpenNext, AWS, and Google Cloud, and the commitments we're making.
nextjs.org/nextjs-acro...
I personally would recommend reviewing actions/checkout with a custom ref input instead. actions/checkout is the way to escape trust boundaries. In pull_request_target events that's fork -> upstream. But in workflow_dispatch events actions/checkout allows running in protected GH environments.
From Chrome 145 (on general release next week!), DevTools we will start to show so called "soft" navigations and "Soft LCP" in the Performance Panel traces.
These are for SPAs which don't do a full page load, but instead "fake it" by updating the current page and pushing a new history entry.
1/5 🧵
The "export defer" TC39 proposal aims to introduce a similar optimization *at the language level*, so that you can rely on it in all the tools and environments that you might run your code with.
Just because you need one thing from a module, you shouldn't pay the cost of all the others!