He can’t keep getting away with this
Maybe the real treasure was the directives we made along the way
Jimmy Lai
1,139 posts
Jimmy Lai
@feedthejim
- dear self-hosted users of Next.js, what can we do to make your life easier?
- Next 15 headline: "caching is hard." 👀 The release is happening very soon and there are three changes that I'm really really excited about. ◆ no more fetch caching by default ✅ ◆ no more client caching by default ✅ ◆ no more static GET routes by default ✅
- ✨ Introducing Typescript support for next.config.js in Next.js 15 h/t to @devjiwonchoi for his first major ship as a member of the Next.js team. What an exciting start! ◆ Native support for next.config.ts (and other TS file extensions). ◆ HMR on config changes. ◆ Available
- We’ve made some significant DX improvements in Next.js on 15 canary over the past few months that we've been dying to share with you, particularly with Turbopack’s stability and performance—it’s been a pleasure to use. After reviewing the results of the poll on Next 15 RC
- Today's a good day to announce that I've taken up the engineering manager position for the Next.js team for a few weeks now and that it's finally official :) I'm super excited to be able to support my team in making the framework better. Lots of good changes coming soon 🥰
- I was waiting until we got something concrete to announce but yolo: we are actively working with the folks from OpenNext and other partners to ship an official build adapter API for Next.js and make it easier to for anyone to support deploying Next.js’ more advanced capabilities.Replying to @leerob. @leerob is class act. He DM with me yesterday to discuss how to better handle security issues with @nextjs in the future and plans for adding adapters to make it easier for @Netlify@Cloudflare support.
- wait, what are we shipping at the Next.js Conf then? 👀Next.js 15 and Turbopack Dev are now stable. Upgrade automatically with our new CLI and codemods. nextjs.org/15
- If you want to try out the new React Compiler with Next.js and don't want to wait until next week for a Next.js 15 announcement 👀, here's how. ◆ Run `pnpm install next@canary react@rc react-dom@rc babel-plugin-react-compiler`. ◆ Enable this option in your next.config.js file:the React Compiler is gonna be usable day one with a vanilla babel config for Next.js, but we’re gonna have a slightly better integration with this PR by @_ojkwon: github.com/vercel/next.js… Stay tuned for Next.js announcements next week :)
- Replying to @adamwathantl;dr: it's on purpose, but we're open to change; please send us feedback! A core part of the App Router design was to shape the APIs and concepts so we could push performance beyond what a standard SSR framework can achieve. One major choice was to separate the rendering of
- the React Compiler is gonna be usable day one with a vanilla babel config for Next.js, but we’re gonna have a slightly better integration with this PR by @_ojkwon: github.com/vercel/next.js… Stay tuned for Next.js announcements next week :)
- Next.js platform adapters are coming to you sooner than you think :) build once, deploy everywhere
- I’ve been wanting to improve error handling in Next.js for a long time, and this release is a huge step forward. A sleek UI, clearer messages, and real fixes, not just weird cryptic errors. And this is just the foundation… Next.js Devtools are on the way!Next.js 15.2 • Redesigned Error UI & Improved Stack Traces • Streaming Metadata • Turbopack Performance Improvements • View Transitions (experimental) • Node.js Middleware (experimental) nextjs.org/blog/next-15-2
- The Next.js documentation website now includes a version selector, let us know what you think! nextjs.org/docs
