Learn about the hidden cost with JavaScript runtimes.
By optimizing package imports, we’ve seen 40% faster cold boots when using libraries with many barrel files.
vercel.com/blog/how-we-optim…
It happened! I’ve open sourced my exif-based photo blog as a (near) zero-config @vercel template. It uses all the things:
◆ Next.js App Router with Server Actions
◆ Next.js Image
◆ Next Auth
◆ Vercel Postgres
◆ Vercel Blob
◆ Vercel OG
Template → vercel.fyi/photo-blog
Generative AI has spawned thousands of new products.
But outside of ChatGPT, what are everyday consumers using? What's growing, and what has flattened?
We crunched the numbers to find the top 50 consumer web products by monthly visits - here's our learnings ⬇️
Love seeing the growth of @nextjs in the top 1M sites on the web.
The App Router is now growing 80% MoM on average as more of these sites upgrade to v13.
New release landing soon 😁
ALT A chart showing the 80% growth of the Next.js App Router in the top 1 million sites on the web, based on the HTTP archive
✨ New @nextjs docs: Forms & Mutations!
Including revalidating cached data, loading & error states, server actions, form validation, reading cookies and headers, and more.
Both JS/TS and Pages/App Router!
nextjs.org/docs/app/building…
We've been running the @nextjs job board on Github Discussions for 1.5 years now!
150+ companies like Walmart and Sony have posted jobs and several hundred developers have posted their profiles.
I love getting emails like this from devs who landed jobs through it 🖤
ALT Screenshots of emails I got from people who got jobs from the Next.js GitHub Discussion job boards
Our Website Team has finished a long-term infrastructure transition of the Node.js Website! 🌠
This will have significant improvements in reliability, performance and speed. Big thanks to @vercel for hosting our project infrastructure. 💚
Next.js 13.4.8 includes improvements for compiler performance and various bug fixes.
On Vercel.com, this led to 1.5x faster local server startup and 54% faster updates when making changes (HMR / React Fast Refresh).
Here are the changes we've made to improve performance ↓
◆ Doing less work by caching or minimizing slow operations
◆ Optimizing expensive file system operations
◆ More incrementally traversing trees during compilation
While these updates are more about the underlying tools like bundlers and compilers, we thought it would be interesting to share some of the work we’ve done.
For example, to improve the local server startup (next dev) we’ve:
◆ Improved the traversal of the client / server graph, removing 100ms
◆ Moved unnecessary blocking synchronous calls to be lazy, removing 70ms
◆ Reduced initial compilation to only need either pages or app routes instead of both, removing up to 500ms
To improve HMR / React Fast Refresh, we’ve:
◆ Added a shared cache for file system calls between different compilation phases
◆ Optimized file resolution for deeply nested directories, improving cold compilation by 30%
◆ Improved revalidation heuristic to prevent blocking the main thread, removed 1-2s on large pages
We’ve also added default configurations for popular libraries with `modularizeImports`. This ensures you don’t accidentally try to reload thousands of additional modules, typically found with icon libraries.
These performance improvements and various bug fixes are available today in 13.4.8. Our current focus remains optimizing performance and reliability, so expect more updates like this in the next release.
github.com/vercel/next.js/re…