Jimmy Lai

we're working hard on it! I'm leaning more towards sharing new things when they're fully ready but it is true that we could have shared a little more

26.06.2025 14:02 — 👍 5    🔁 0    💬 0    📌 0

we'll share more about this next week, but Turbopack is there to stay :)

27.02.2025 15:23 — 👍 15    🔁 0    💬 1    📌 0

Next.js 15.2 Next.js 15.2 introduces an improved error experience, streaming metadata, Turbopack performance improvements, and more.

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

27.02.2025 01:36 — 👍 143    🔁 23    💬 3    📌 5

Screenshot showing the Chrome DevTools Performance tab with RSC integration.

I'm working on built-in profiling of both Client and Server Components in Chrome DevTools Performance tab. Thanks to the new performance.measure() extensions. h/t Andrés Olivares

This works in any RSC environment. In fact, this screenshot is running RSC for Parcel. h/t @devongovett.bsky.social

12.12.2024 04:25 — 👍 188    🔁 23    💬 3    📌 2

yeah that's new in 15 :)

02.12.2024 12:21 — 👍 0    🔁 0    💬 1    📌 0

Spotify: “please trust us with all of your music”

Also Spotify: “I’m gonna slowly remove random tracks from your Liked Songs over time and watch you slowly spiral into insanity as you question whether or not you already knew this song”

24.11.2024 09:27 — 👍 3    🔁 0    💬 0    📌 0

Let me know if you find something 🙏 a screenshot of the error would be enough

15.11.2024 16:03 — 👍 0    🔁 0    💬 0    📌 0

A common reason this can occur sometimes is that some browser extensions inject data attributes to the head or body during page load, which will fire React's alarms. Grammarly does this to me, for example. I recommend disabling extensions in dev.

15.11.2024 15:41 — 👍 1    🔁 0    💬 1    📌 0

Hey Maggie, I'm a team member; thanks for the report. I just tested on a fresh Next.js Boilerplate, and I could not repro it in dev or production.

Is that the template you used? If so, could you provide a screenshot of the error?

15.11.2024 15:41 — 👍 0    🔁 0    💬 1    📌 0

we’re also gonna introduce a new refresh() api to do this directly from a server action in 15.1 instead of doing this at the client level

13.11.2024 11:25 — 👍 6    🔁 1    💬 0    📌 0

it’s gonna take us some time but we’re gonna get there 🫡

had a really promising chat with @orinokai.bsky.social today about how Netlify’s Next adapter works and how we could do better, we just need to ship now

06.11.2024 21:22 — 👍 2    🔁 0    💬 1    📌 0

That’s a really well written article 🙏 it’s quite interesting seeing our work from this perspective

06.11.2024 21:17 — 👍 1    🔁 0    💬 1    📌 0