Log inSign up
Tim
Vercel
10.2K posts
Tim profile banner
@timneutkens

Tim

Vercel
@timneutkens
@vercel. co-author of @nextjs, MDX, Micro, and ncc. Opinions are my own.
The Netherlands
Joined February 2013
591
Following
53.9K
Followers
RepliesRepliesRepostsRepostsMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • @timneutkens
    Tim
    Vercel
    @timneutkens
    16h
    We’ve resolved 1500 issues, reducing duplicates, already fixed issues, and issues that no longer reproduce in the latest version. Incredibly excited about the research and work Marcos did to consistently investigate and reproduce new issue reports. Learn more in the post!
    @nextjs
    Next.js
    Vercel
    @nextjs
    16h
    We closed 1,500 issues on 𝚟𝚎𝚛𝚌𝚎𝚕/𝚗𝚎𝚡𝚝.𝚓𝚜 in one month by building a 𝚌𝚕𝚘𝚜𝚊𝚋𝚒𝚕𝚒𝚝𝚢 agent with @eve. The workflow: 1. Search related work 2. Try to reproduce bugs across versions in a sandbox 3. Return context for review nextjs.org/blog/how-we-cl…
    4
  • @timneutkens
    Tim
    Vercel
    @timneutkens
    Aug 19
    We're the Next.js team. Ask us anything! We recently shipped Next.js 16.3, and we’re excited to talk about what’s new, how we approached the release, where we are going, and what we’ve learned while building and maintaining Next. Ask us anything about Next 16.3, App Router,
    Image
    105
  • @timneutkens
    Tim
    Vercel
    @timneutkens
    Aug 18
    Next.js team AMA is live now!
    Image
    From the nextjs community on Reddit
    From reddit.com
    2
  • @timneutkens
    Tim
    Vercel
    @timneutkens
    Jul 23
    Available now on next@preview! (16.3.0-preview.9)
    @rauchg
    Guillermo Rauch
    Vercel
    @rauchg
    Jul 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
    5
  • @timneutkens
    Tim
    Vercel
    @timneutkens
    Jul 23
    Available now on next@preview! (16.3.0-preview.9)
    @timneutkens
    Tim
    Vercel
    @timneutkens
    Jul 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
    Image
    5
Advertisement
Advertisement