Andrew Imm

Turbopack and @nextjs at @vercel

[Andrew Imm @setimmediate]

Fresh new look for https://t.co/D7e3j2C6cA 👀
https://t.co/lZ4UXhRy9A

[Next.js @nextjs]

The Next.js site has a new look!

We've redesigned the homepage, /docs, /blog, and more, with a consistent design that keeps the focus on the content.

https://t.co/S5DGXywqm5

A few highlights ↓

[Andrew Imm @setimmediate]

@maiconsanson @aurorascharff We are working on persistent “use cache” across deployments. Most of the work is done, but it’s untested so we don’t feel comfortable enabling it by default yet. Cache invalidation is the hardest problem in CS, right? If tests look good, it should arrive in a minor release soon.

[Andrew Imm @setimmediate]

Fantastic blog post from our intern @sam_poder about one of the many features he shipped.

The future of framework features isn't flags, it's weights. Your agents can tune the optimal settings for your app. Some pages need more JS chunks, some need fewer.

https://t.co/aUXpcXloiu

[Next.js @nextjs]

Your Next.js app ships dozens of JavaScript chunks. Turbopack has to balance how many requests a page makes against how much code it ships.

Learn how it works and what's new in Next.js 16.3.

https://t.co/6QO8vKbqzT

[Andrew Imm @setimmediate]

@naman34 @stylexjs When I left Meta I was afraid to assert my love of stylex. It must be affinity bias. Stockholm syndrome. Everyone out here is using Tailwind.

I'm glad folks are realizing it's a really well thought out solution. It's battle-tested in a way most projects never are.

[Andrew Imm @setimmediate]

@Mad__Kat @lukeisandberg @devongovett @boshen_c @stanzilla Outside of swc plugin, how would you propose integrating the react compiler with webpack? It’s native code, it either needs to run as wasm or as a custom napi binary. You could shell out to a cli but I can’t imagine that working well with a webpack loader

[Andrew Imm @setimmediate]

@Mad__Kat @lukeisandberg @devongovett @boshen_c @stanzilla You could compile the SWC version to a WASM SWC plugin, which should work with any Next bundler. I did this to test the initial Rust port, which gave us the confidence to bake it directly into Turbopack. Cold start on those plugins is rough, though.

[Andrew Imm @setimmediate]

@timneutkens @cramforce @phiandersson Beyond the changes in that blog post, the team has also managed to cut memory the traditional way: freeing bytes that are no longer relevant, and slimming down data structures. Sometimes cutting a struct from 16 bytes to 8 is meaningful if it has 10 million+ instances

[Andrew Imm @setimmediate]

The Turbopack team put so many wins into this:
▸ Up to 90% less memory in dev
▸ Persistent cache across builds
▸ Static assets can be re-used across builds
▸ Improved tree shaking
▸ Experimental new chunking methods for both JS and CSS

Truly an epic release.

[Next.js @nextjs]

Next.js 16.3 is now available!

• Up to 90% less memory in dev
• Faster builds, type checking, and rendering
• Better tooling for AI agents
• Custom error boundaries
• Instant Navigations for SPA-like responsiveness

https://t.co/lNAQqpAKT1

Here's what's new ↓

[Andrew Imm @setimmediate]

@philw_ @nextjs @timneutkens Security RSS feed is live! Thanks again for giving us the idea.

https://t.co/ZvyrVQoDVX

[Next.js @nextjs]

We've added a security-only RSS feed so you can follow advisories and patches without watching the full changelog.

Subscribe to stay up to date on future security releases.

https://t.co/B2tjyonxC0
https://t.co/woOroqDWNy

[Andrew Imm @setimmediate]

@anthonysheww Buying my tickets for the Turboverse now

[Andrew Imm @setimmediate]

@ashraf_chowdury @rauchg @nextjs The new instant navigation features are for App Router, but the Turbopack improvements will benefit everyone. Same with the AI coding enhancements.

[Andrew Imm @setimmediate]

@wztlink1013 We're looking into it. Windows makes symlinks difficult.
Thanks for tying the preview. This kind of feedback makes the stable release even more reliable.

[Andrew Imm @setimmediate]

Next.js users talked, we listened.
Turbopack in 16.3 is a MASSIVE improvement for memory usage.
I heard from a user this morning who cut 95% of their devserver memory just by upgrading to the 16.3 preview. I'm excited to get this out to all Next.js users.
https://t.co/FLgpAgbqaZ

[Andrew Imm @setimmediate]

@thiagoperes @aurorascharff Try next@preview which is the pre-release 16.3. I want to hear if it solves your problem - if not I want to get to the bottom of it.

[Andrew Imm @setimmediate]

@thiagoperes @aurorascharff It actually does. For months Turbopack has been restructuring the in-memory cache so that it can be evicted from RAM when it's written to disk.
Previous memory usage went 📈 as you compiled and cached more routes.
Now it looks like a GC'd sawtooth pattern 🪚

[Andrew Imm @setimmediate]

@timneutkens @colinhacks We were exploring something similar yesterday.
It's hard to faithfully watch symlinks that point outside the repo, and we've seen bugs where pnpm changing the source of truth caused nasty issues. But there are legit cases we should be able to trust. Adding this to the discussion.

[Andrew Imm @setimmediate]

@poteto @vercel Let’s figure out a plan for publishing official crates! I don’t want to make the turbopack team responsible for managing forks

[Andrew Imm @setimmediate]

Rust React Compiler is merged!
We tested it at @vercel on sites like v0:

SWC plugin had a long WASM cold start, but great wins over the OG Compiler.
Linking the code directly into Turbopack is even better: >40% faster compilation.

PRs coming soon to get this in Next.js 16.4

[Andrew Imm @setimmediate]

@sebastienlorber Everyone should be picking this up. We saw 30-50% faster compilation for large Next.js routes, so we're linking the Rust Compiler directly into Turbopack.

https://t.co/mpusmT73fd

[Andrew Imm @setimmediate]

Rust React Compiler is merged!
We tested it at @vercel on sites like v0:

SWC plugin had a long WASM cold start, but great wins over the OG Compiler.
Linking the code directly into Turbopack is even better: >40% faster compilation.

PRs coming soon to get this in Next.js 16.4

[Andrew Imm @setimmediate]

@tadeumaia @timneutkens What version of Next?
You could export a trace of what next-server is doing and have your agent analyze the memory spans. I could probably give you a prompt to explain the file format to an agent