As AI generates more our code, what'll set great engineers apart isn’t their ability to write complex logic, but their ability to QA proposed solutions.
5
4
1
46
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.
35
44
8
1,075
0
You can now visit nextjs.org/docs/llms.txt 🤖 — There's an `llms-full` version too. You can also add `.md` to any docs link. Only for docs of the latest Next.js version.
3
4
2
36
It is more accurate to use the MDN description: "One or more of the CSS transform functions to be applied. The transform functions are multiplied in order from left to right, meaning that composite transforms are effectively applied in order from right to left." But I always glossed over it because I assumed it was describing different functions. It never clicked that you could use the same function more than once without overriding the earlier one or making the definition invalid. The other thing this description highlights is that order matters: rotate(a) translateX(b) is different from translateX(b) rotate(a).
1
40
TIL multiple CSS transform functions of the same type are additive. I used it to add a turbulence effect that doesn't overwrite existing or in-progress transforms.
In the past, we've given advice on Data Security in Next.js but that information was scattered. I've consolidated everything into a guide. Let me know if there's anything else you'd like to know about. nextjs.org/docs/app/guides/d…
6
11
1
174
We've written two new guides on navigation in Next.js. 1. How navigation works and how to optimize it: nextjs.org/docs/app/getting-… 2. Prefetching (advanced): nextjs.org/docs/app/guides/p…
8
28
1
400
Excited to welcome @icyJoseph_dev to the Next.js docs team! If you've spent time on our Github repo, you've probably bumped into one of his answers. He has consistently topped the most helpful contributors every month. His knowledge will make the docs even better 💎
6
2
118
Docs · nextjs.org/docs/app/building… Is `loading.js` the same as a `<Suspense>` boundary? Not quite. `loading.js` becomes the fallback UI of a Suspense boundary, but because it is a convention, it can be rendered and prefetched ahead of time. Regular Suspense boundaries need a server round-trip to render their fallback. So, are suspense boundaries bad? No. You can use Suspense deeper in a Page to break up rendering into smaller chunks and stream them as they become available. Since the page is already rendering on the server at that point, no additional round-trip is needed. What about static pages? Pages rendered at build time don't need a `loading.js` file because all their content is already available and can be prefetched when <Link>'d to.
2
2
40
A navigation to a dynamic server-rendered page is blocked until the server responds. In Next.js, the first step to improving the experience is to add a `loading.js` file. This unblocks navigation and gives the user feedback while the content streams in.
Vercel Web Analytics, now: • Up to 20× more included events • Up to 80% cheaper for additional events
See you soon ▲ The adjustments load in as the badge is flying around 🤯
Playing around with 'use cache' for a new guide I'm working on. Put together some basic examples at the route, component, and function level. Also gave the playground a glow-up: tweaked the design, added Geist and images, and the gradient borders are finally out, sooo 2022 💁‍♀️
7
17
329
0
Vercel: Recent price reductions Underlying infrastructure improvements → Customer savings
Recent Vercel price drops: 🆕 ~50% off intl. Fast Data Transfer⁰ ✅ ~85% off Functions → Fluid¹ ✅ ~87% off Monitoring → Observability² ✅ ~50% off Domains³ ✅ ~75% off Log Drains⁴ ✅ ~65% off ISR read/writes⁵ ✅ Lower Image Optimization pricing⁶ 🔜 More self-serve products 🔜 More infra optimizations ⁰ vercel.com/changelog/lower-p… ¹ vercel.com/blog/introducing-… ² vercel.com/changelog/vercel-… ³ vercel.com/changelog/lower-p…vercel.com/changelog/lower-p…vercel.com/blog/isr-on-verce…vercel.com/changelog/faster-…
• Blog: nextjs.org/blog/next-15-3 • More info:
Excited to bring you the first version of "next build --turbopack"! Looking forward to seeing the results and iterating quickly towards stability. If you have feedback, let us know! Next up: Tests: 57 tests left. Though we don't expected most applications to run into these cases. Bundle Size: There's some optimizations we still have to implement. Getting more data from real applications will also help in tweaking the chunking heuristics to be optimal for most applications. Persistent Caching: We're in the process of dogfooding disk caching at Vercel to catch edge cases, once these edge cases have been resolved you'll be able to try it out. GitHub Issues: Focus on fixing feedback from early adopters. Performance Improvements: As we get more real-world data we'll be able to optimize further, Turbopack will get faster over time as we identify common patterns across more applications. Proud of the Turbopack team. This is a big milestone that we've been working towards since Next.js 15 was released. Now on towards `next build --turbopack` stable.
6
Next.js 15.3: `next build --turbopack` (alpha) Although some projects may see build speed improvements, the focus of this release is broader adoption to help surface any remaining issues before stabilizing. More optimizations are coming soon.
More client-orientated features coming soon 😘 • Shipped @gao_jude • Docs: nextjs.org/docs/app/api-refe… • Playground with code examples: app-router.vercel.app/use-li…
1
1
1
65