تسجيل الدخولتسجيل
user avatar
Tim
Vercel
@timneutkens
@vercel. co-author of @nextjs, MDX, Micro, and ncc. Opinions are my own.
The Netherlands
انضم في February 2013
588
متابَع
53.3 ألف
المتابِعون
الردودالوسائط
  • user avatar
    Tim
    Vercel
    @timneutkens
    3 أغسطس
    Next.js 16.3 is here! Even more performance and DX improvements coming soon!
    user avatar
    Next.js
    Vercel
    @nextjs
    3 أغسطس
    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 nextjs.org/blog/next-16-3 Here's what's new ↓
  • user avatar
    Tim
    Vercel
    @timneutkens
    23 يوليو
    Available now on next@preview! (16.3.0-preview.9)
    user avatar
    Guillermo Rauch
    Vercel
    @rauchg
    23 يوليو
    Fable just found a 15-30% memory efficiency improvement in Turbopack / Next.js, nearly autonomously. @tobi asked me today: what have been your “holy s***” moments with AI? My answer was: it’s every single week. And it’s accelerating. In fact, “WTFs/day” might just be my
  • user avatar
    Tim
    Vercel
    @timneutkens
    23 يوليو
    Available now on next@preview! (16.3.0-preview.9)
    user avatar
    Tim
    Vercel
    @timneutkens
    22 يوليو
    Reduced React Server Components rendering time in development by up to 73% Details: Many frameworks (including Next.js) use higher stacktrace limits in development in order to make sure that e.g. errors happening in deeply nested code / node_modules have a clear stack when
  • user avatar
    Tim
    Vercel
    @timneutkens
    23 يوليو
    We made a significant performance improvement to Instant Validation in the Next.js 16.3 preview. If you're currently using next@preview be sure to upgrade! See video for before/after. Note: "before" was only when using cache components on next@preview. If you're on any other
    00:00
  • user avatar
    Tim
    Vercel
    @timneutkens
    22 يوليو
    Reduced React Server Components rendering time in development by up to 73% Details: Many frameworks (including Next.js) use higher stacktrace limits in development in order to make sure that e.g. errors happening in deeply nested code / node_modules have a clear stack when