Jimmy Lai @feedthej.im · 26/06/2025we'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 050
Jimmy Lai @feedthej.im · 27/02/2025we'll share more about this next week, but Turbopack is there to stay :) 1150
Reposted by Jimmy LaiNext.js @nextjs.org · 27/02/2025Next.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-2nextjs.orgNext.js 15.2Next.js 15.2 introduces an improved error experience, streaming metadata, Turbopack performance improvements, and more. 313822
Reposted by Jimmy LaiSebastian Markbåge @sebmarkbage.calyptus.eu · 12/12/2024I'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 318923
Jimmy Lai @feedthej.im · 24/11/2024Spotify: “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” 030
Jimmy Lai @feedthej.im · 15/11/2024Let me know if you find something 🙏 a screenshot of the error would be enough 000
Jimmy Lai @feedthej.im · 15/11/2024A 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. 110
Jimmy Lai @feedthej.im · 15/11/2024Hey 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? 100
Jimmy Lai @feedthej.im · 13/11/2024we’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 061
Jimmy Lai @feedthej.im · 06/11/2024it’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 120
Jimmy Lai @feedthej.im · 06/11/2024That’s a really well written article 🙏 it’s quite interesting seeing our work from this perspective 110
