Pinned Tweet
I'm excited to share that I'm joining @vercel as a DX Engineer!
For the past few years, I've been writing blog posts, giving talks, and building demo apps around React and Next.js, all on my own time, because I genuinely love it. The deep dives into patterns, the experiments ent that helps other developers get unstuck: that's been the most rewarding part of my career so far.
Now I get to do it as part of the team that builds the framework.
Can't wait to start this journey, teach what I learn along the way, and help make Next.js and Vercel products as good as possible for everyone.
My inbox is always open.
For the past few years, I've been writing blog posts, giving talks, and building demo apps around React and Next.js, all on my own time, because I genuinely love it. The deep dives into patterns, the experiments ent that helps other developers get unstuck: that's been the most rewarding part of my career so far.
Now I get to do it as part of the team that builds the framework.
Can't wait to start this journey, teach what I learn along the way, and help make Next.js and Vercel products as good as possible for everyone.
My inbox is always open.
188
26
1,372
59,997
Aurora Scharff retweeted
Everybody will be here. You?
Our first official React Foundation Meetup is here! π Nov 11 Β· 6β9:30 PM GMT
π Meta Kings Cross, London
Join us for good people, good food, and good times!
RSVP HEREπ luma.com/g9q690i2
Our first official React Foundation Meetup is here! π Nov 11 Β· 6β9:30 PM GMT
π Meta Kings Cross, London
Join us for good people, good food, and good times!
RSVP HEREπ luma.com/g9q690i2
3
7
42
2,606
Ahead of Next.js 16.4, I worked on applying the upcoming features across v0 and validating our new Partial Prefetching optimizer Skill in a real app.
The post includes before-and-after videos of the navigation experience and walks through the caching, prefetching, and production checks behind the refactor.
Excited to finally share it!
The post includes before-and-after videos of the navigation experience and walks through the caching, prefetching, and production checks behind the refactor.
Excited to finally share it!
We used a coding agent with Next.js 16.4's new prefetching controls and Skill to improve v0's navigation experience at no added cost.
The loop:
β’ Capture navigation with πππππππ()
β’ Define the target UI in the test
β’ Refactor until it passes
nextjs.org/blog/improvingβ¦
1
7
110
6,285
Aurora Scharff retweeted
We used a coding agent with Next.js 16.4's new prefetching controls and Skill to improve v0's navigation experience at no added cost.
The loop:
β’ Capture navigation with πππππππ()
β’ Define the target UI in the test
β’ Refactor until it passes
nextjs.org/blog/improvingβ¦
The loop:
β’ Capture navigation with πππππππ()
β’ Define the target UI in the test
β’ Refactor until it passes
nextjs.org/blog/improvingβ¦
23
28
390
29,060
Aurora Scharff retweeted
The first batch of speakers is here! and the stage at JSworld has never looked better. π
Just some of the faces you can expect to see:
Evan You (@evanyou): Creator of Vue & Vite
Tim Neutkens (@timneutkens): Next.js Lead
Matteo Collina (@matteocollina): Co-founder and CTO at PlatC member
Aurora Scharff (@aurorascharff): DX, Docs & Education at Next.js team
Kitze (@thekitze): Creator of Sizzy, Benju, Glink, React Academy, and Jsui
Luca Mezzalira (@lucamezzalira): Director at 50 cents media
Nina Togunakova: Engineer at Evil Martians
Sacha Greif (@SachaGreif): Creator of State of Javascript, AI, Devs Surveys
Maya Shavin (@MayaShavin): Staff Engineer at Salesforce
Matheus Albuquerque (@ythecombinator): Staff Software Engineer at Medallia
Just some of the faces you can expect to see:
Evan You (@evanyou): Creator of Vue & Vite
Tim Neutkens (@timneutkens): Next.js Lead
Matteo Collina (@matteocollina): Co-founder and CTO at PlatC member
Aurora Scharff (@aurorascharff): DX, Docs & Education at Next.js team
Kitze (@thekitze): Creator of Sizzy, Benju, Glink, React Academy, and Jsui
Luca Mezzalira (@lucamezzalira): Director at 50 cents media
Nina Togunakova: Engineer at Evil Martians
Sacha Greif (@SachaGreif): Creator of State of Javascript, AI, Devs Surveys
Maya Shavin (@MayaShavin): Staff Engineer at Salesforce
Matheus Albuquerque (@ythecombinator): Staff Software Engineer at Medallia
0
6
20
3,406
The new design is super sleek!! I spend a lot of time in the docs and itβs so much easier to navigate around and read content now!
Great work @yavorpunchev @kindlaar @mike_wagz
Great work @yavorpunchev @kindlaar @mike_wagz
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.
nextjs.org
A few highlights β
3
2
112
4,274
Aurora Scharff retweeted
β¦one of the design engineers working on this had a baby whilst we were making this baby.
Shoutout @yavorpunchev @mike_wagz @marijanapav @kindlaar @aurorascharff
Shoutout @yavorpunchev @mike_wagz @marijanapav @kindlaar @aurorascharff
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.
nextjs.org
A few highlights β
1
2
46
2,699
Aurora Scharff retweeted
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.
nextjs.org
A few highlights β
We've redesigned the homepage, /docs, /blog, and more, with a consistent design that keeps the focus on the content.
nextjs.org
A few highlights β
29
53
831
61,635
Coding agents hit Next.js errors, unclear docs, and non-obvious workarounds while they build. They often solve the task and move on without reporting what failed, what they tried, or what finally worked.
For Next.js 16.4, we created a new agent feedback system. Enable it in your ππππππ: {
ππππππ΅πππππππ: ππππ,
}
If your agent finds a potential Next.js issue, it can open a report in your browser before finishing. The report explains what happened, what the agent expected, and any workaround it found. You can edit or discard it, and nothing is sent until you hit "Send feedback".
We group submitted reports to find recurring problems and use them to improve framework behavior, error messages, docs, and tooling.
If you try it, let me know how the experience goes and what we should improve!
Docs below β
For Next.js 16.4, we created a new agent feedback system. Enable it in your ππππππ: {
ππππππ΅πππππππ: ππππ,
}
If your agent finds a potential Next.js issue, it can open a report in your browser before finishing. The report explains what happened, what the agent expected, and any workaround it found. You can edit or discard it, and nothing is sent until you hit "Send feedback".
We group submitted reports to find recurring problems and use them to improve framework behavior, error messages, docs, and tooling.
If you try it, let me know how the experience goes and what we should improve!
Docs below β
12
6
102
3,709
Learn how agent feedback works:
nextjs.org/docs/app/guideβ¦
Configure ππππππ΅πππππππ:
nextjs.org/docs/app/api-rβ¦
Read our 16.4 announcement:
nextjs.org/blog/next-16-4β¦
nextjs.org/docs/app/guideβ¦
Configure ππππππ΅πππππππ:
nextjs.org/docs/app/api-rβ¦
Read our 16.4 announcement:
nextjs.org/blog/next-16-4β¦
0
0
7
402
Aurora Scharff retweeted
An out-of-band Next.js security update is planned for Wednesday, October 14.
It will address three vulnerabilities in upstream dependencies, including two critical and one high-severity issue.
nextjs.org/blog/upcoming-β¦
We're also changing how we share future security notices β
It will address three vulnerabilities in upstream dependencies, including two critical and one high-severity issue.
nextjs.org/blog/upcoming-β¦
We're also changing how we share future security notices β
9
22
193
16,634
Iβve been updating an older commerce demo to explore ππππππππππππ in Next.js 16.4.
Cache Components lets you mix static, cached, and request-time content. When you need predictable compute costs, the new ππππππππππππ API lets you guarantee static output Product links in the grid use ππππππππ={ππππ} to load cached details before the click. On /πππππππ/[ππ], ππππππππππππ = 'ππππππππ' keeps personalized cart and saved state out of those prefetches.
On /πππππ, ππππππππππππ = 'ππππππππππ' guarantees the whole page stays static and shows a validation error if request-time work is added.
Live demo, source code, and docs below β
Cache Components lets you mix static, cached, and request-time content. When you need predictable compute costs, the new ππππππππππππ API lets you guarantee static output Product links in the grid use ππππππππ={ππππ} to load cached details before the click. On /πππππππ/[ππ], ππππππππππππ = 'ππππππππ' keeps personalized cart and saved state out of those prefetches.
On /πππππ, ππππππππππππ = 'ππππππππππ' guarantees the whole page stays static and shows a validation error if request-time work is added.
Live demo, source code, and docs below β
2
3
66
2,347
Live demo: next16-commerce.vercel.app
Source code: github.com/aurorascharff/β¦
Learn how to keep pages static: nextjs.org/docs/app/guideβ¦
ππππππππππππ API: nextjs.org/docs/app/api-rβ¦
Read our 16.4 announcement: nextjs.org/blog/next-16-4β¦
Source code: github.com/aurorascharff/β¦
Learn how to keep pages static: nextjs.org/docs/app/guideβ¦
ππππππππππππ API: nextjs.org/docs/app/api-rβ¦
Read our 16.4 announcement: nextjs.org/blog/next-16-4β¦
0
1
5
347
Aurora Scharff retweeted
En la JSCONFMX tenemos a los mejores en nuestro escenario. Speakers traΓdos de Google, Vercel, Github, NYTimes, Netflix, IBM y un montΓ³n de empresas mΓ‘s que estΓ‘n cambiando la forma de crear la web. π₯
π ΓLTIMOS BOLETOS jsconf.mx
π ΓLTIMOS BOLETOS jsconf.mx
0
5
17
2,525
Aurora Scharff retweeted
@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.
1
1
5
276
I built Stamp, a Gmail-style inbox, to explore the new ππππππππππ() API in Next.js 16.4.
Sometimes you want to cache content for return visits without prefetching it before someone opens the page.
In this mailbox, visible links prefetch each thread's header. The e 'πππ πππππ', but ππ πππ ππππππππππ() keeps them out of the prefetch. They load after the click but will still be reused when you return.
Live demo, source code, and docs below β
Sometimes you want to cache content for return visits without prefetching it before someone opens the page.
In this mailbox, visible links prefetch each thread's header. The e 'πππ πππππ', but ππ πππ ππππππππππ() keeps them out of the prefetch. They load after the click but will still be reused when you return.
Live demo, source code, and docs below β
9
17
153
5,708
Live demo: next16-mail.vercel.app
Source code: github.com/aurorascharff/β¦
Learn how to control what gets prefetched: nextjs.org/docs/app/guideβ¦
The ππππππππππ() API: nextjs.org/docs/app/api-rβ¦
Read our 16.4 announcement: nextjs.org/blog/next-16-4
Source code: github.com/aurorascharff/β¦
Learn how to control what gets prefetched: nextjs.org/docs/app/guideβ¦
The ππππππππππ() API: nextjs.org/docs/app/api-rβ¦
Read our 16.4 announcement: nextjs.org/blog/next-16-4
0
0
11
571
Aurora Scharff retweeted
@aurorascharff @brenelz @nextjs i think the important thing to highlight is that with Partial Prefetching, a grid of 100 "/product/<id>" Links will be *one request* by default (it's only more if you turn on prefetch={true} for some of them)
1
1
6
385
Aurora Scharff retweeted
Trying this on my wifeβs business website. Prefetch the main product UI, defer the heavier secondary bits until they actually open the page π€
Next.js 16.4 adds ππππππππππ(), a new API for keeping parts of a route out of prefetches until someone actually navigates.
I built Stamp, a mailbox inspired by the example in the release post, to try it. Visible rows prefetch thread headers, while message bodies wait for navigation, so scrolling never downloads emails you don't open.
Demo: next16-mail.vercel.app
Source: github.com/aurorascharff/β¦
1
1
3
348
Aurora Scharff retweeted
Self-improving Next.js
Version 0 -> Agent Feedback -> Software Factory -> Agentic Upgrade -> Version 1
β¦
Version N -> Agent Feedback -> Software Factory -> Agentic Upgrade -> Version N+1
β¦ and the loop continues
Version 0 -> Agent Feedback -> Software Factory -> Agentic Upgrade -> Version 1
β¦
Version N -> Agent Feedback -> Software Factory -> Agentic Upgrade -> Version N+1
β¦ and the loop continues
Next.js 16.4
β’ Cache Components by default in new apps
β’ Static output guarantees and more control over prefetching
β’ Agent-guided upgrades and feedback
β’ 20β25% smaller Turbopack disk cache
β’ Faster development and smaller bundles
nextjs.org/blog/next-16-4
2
2
18
1,185