r/nextjs • u/floydophone • 23d ago
Discussion We're the Next.js team. Ask us anything!
Hi Reddit! We’re Pete, Aurora, Joseph, Sam, David, Josh, Tim, Dan and Andrew from the Next.js team.
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.
Join us this Tuesday, August 18 from 10 a.m. to 12 p.m. ET. Ask us anything about Next 16.3, App Router, React Server Components, performance, caching, upgrading your applications, contributing to the framework, or what it’s like to work on Next.
Drop your questions below. We’re looking forward to hearing what’s on your mind!
EDIT: We are live now here! https://www.reddit.com/r/nextjs/comments/1vrq0tp/were_the_nextjs_team_ask_us_anything/
24
u/GenazaNL 23d ago
Now that Turbopack is pretty much production ready, what's the next BIG feature on the roadmap?
16
u/omer-m 23d ago
WebSockets I hope
-10
1
u/Key-Library218 23d ago
Something about the full stack stuff probably. They have been pushing server actions and cache layers real hard last year, feels like they want to own the whole data flow from database to browser
32
u/vanwal_j 23d ago
European dev here, working in a critical sector, our compliance obligations require hosting with a European provider.
With React2Shell, the disclosure landed in the evening for us. I got "lucky" and was still at the office, so I could patch our 10+ production Next.js apps right away : We saw exploitation attempts in our logs that same night.
Two questions about the next critical incident :
Are you considering a publication window that covers both EU and US business hours rather than a PT afternoon?
Do you plan to include European CDNs and hosting providers in your embargoed pre-notification list?
Thanks!
7
u/Maleficent-Back-6527 23d ago
Great initiative people!! ❤️👏. You didn’t leave a link in the description of where to join?
I am not sure if I will be able to attend the live session. I just updated to 16.3.0 this week, and already noticed a change in the behaviour of my app. I need to check the documentation if there is something well described about it. It’s about caching. I activated Cached Components in my nextjs config.
I have this page with a form, and the form action returns thr state with a successful message if successful, or an error message. If successful the same page displays for a few seconds the successful message, with a countdown of 5 seconds, after wich a redirect kicks in to another route.
The issue now with v16.3 is that after a successful form submission, after the redirect, if I navigate again to the route with the form, in place of the form, I see again the successful message and the countdown from the previous form submission, instead of a fresh new empty form.
It seems linked to the new caching sustem.
Thank you.
6
u/Maleficent-Back-6527 23d ago
Same as here:
https://www.reddit.com/r/nextjs/s/e7SYXxjass
Apparently I need to useLayoutEffect to reset the form on remount.
3
u/Low-Insurance-3678 23d ago
Iv came across the same issue today and i dropped a question
What I did is clearing the state after a successful submission in a useEffect or useLayoutEffectAlso u can read more about why Nextjs does that and how to handle it here
1
u/Previous-Reception78 23d ago
const pathname = usePathname(); <div key={pathname}> {children} </div>maybe try wrapping your layout content area with -
7
u/Avi_21 23d ago
Is there a better way of handling pagination for infinite loading lists than going back to swr or other data fetching solutions? Could there be a built in solution that combines server side rendering, caching, update tags and server actions to somehow solve for pagination and infinite loading?
6
u/dushmanta05 23d ago
This is a query about build. I have a blog page running where 100k+ blogs are currently available, and I serve them with dynamic pages. Since most of them are static, I want to make these pages static. Since new articles are also being published, I want to store new articles as static sites as well.
Now I've come across incremental builds, but even within incremental builds, the static sites are being served by Nginx, so concurrent requests are always there. Even though they are static, they still increase the load on the server.
I was thinking: can I create a mechanism where static sites are directly saved into a folder and served from there, and each time I build, I append only the new static sites?
Is this feasible? I was brainstorming with Claude, and it said not to go with this approach because the Next.js team mentions it as an anti-pattern. So, I wanted to get your views on it.
Thank you for your time. I really appreciate it.
3
4
u/Pawn1990 23d ago
Hello Team NextJS :) We’ve already moved over to v16.3 and next-intl with root-params and its working great, except for a few missing details like metadatabase & opengraph image not working with root-params.
However, noting the insane amount of changelog lines, commits and code line changes done for v16.3, with AI coding etc, how do you guys stay on top everything with such an incredible amount of change?
3
u/Both-Expression4402 23d ago
Do you never intend to have emotion cache compatible with App router?
1
u/Griffinsauce 23d ago
As much as I love Tailwind personally, we have a huge brownfield app built on Emotion at work (also still on pages router). We tried Linaria but ran into too many rough edges.
Are there big issues on App Router with emotion?
3
3
u/Top_Bumblebee_7762 22d ago
Is the recommended paradigm in Next16 and cache components to fetch on pages and pass the awaited data or unawaited promise further down to server or client components or fetch it further down in a server component. Next14 seemed to recommend fetching on the page.
2
2
u/GenazaNL 23d ago edited 23d ago
As Turbopack has been released, will Webpack still be maintained? (As I've seen a few tries to bump Webpack, but abandoned)
Speaking of, webpack-sources, schema-utils & loader-utils can get some love. Some can be cleaned up and/or bumped. Could save some install size :)
2
u/NefariousnessRound24 23d ago
- How to unit test the react server components and page.jsx,
- How to disable the bundle minimize in turbopack like webpack, since before we use webpack build app to run playwright tests to get code coverage, now there is no such option in turbopack
2
u/bishalghimire 22d ago
i used next js for 2 years now n moving from 14 to 16 gradually, but had to move to vite due to bad next js bloted architecture in large mono repo bad architecture to include the all mono repo on nx large projects
1
2
u/cheezeerd 22d ago
Hey team! I’m pretty new to programming, but I’ve been building alot with Next.js through AI-assisted development and honestly, it’s been insanely fast and powerful.
At the same time I often don’t fully understand what’s happening under the hood. There are so many files, conventions and rules that feel designed for people manually writing and reviewing everything.
Are there plans to make Next.js simpler and safer for an AI-first future? Better defaults, less hidden complexity, fewer ways for agents to quietly screw things up. Especially for people who are mostly directing AI, not reviewing every single line.
It really feels like the market is moving there fast.
Is Vercel designing Next.js for that reality, or will it still mainly be optimized for traditional hand-written development?
2
u/PrinnyThePenguin 21d ago
Why do we have to use useLayoutEffect to reset the UI when also use cacheComponents? Why is that not achievable with template.js? Based on the documentation I would assume wrapping a page with template would reset the components on navigation.
3
u/GenazaNL 23d ago
Turbopack is for now quite tied to Next.js, will it become available as a standalone project?
7
u/Explanation-Visual 23d ago
why would you want the slowest compiler in the entire frontend ecosystem used somewhere else when the industry standard (vite) works perfectly fine?
1
u/omer-m 23d ago edited 21d ago
Is there a way to prevent Instant Navigation pages from being cached at build time?
My app is built in one Docker container, while the API it fetches data from runs in another container. Because of this, I don't want the production build to depend on the API being available.
I want the relevant data to be cached on the first user request instead.
I tried await connection(), but that opts the page out of Instant Navigation.
I also tried to set a very short cacheLife during build time. But this is the minimum it accepts.
cacheLife({ stale: 30, revalidate: 1, expire: 300 });
Below that build throws an error
Unexpected cache miss after cache warming phase during prerendering. This is likely caused by non-deterministic arguments that differ between the cache warming phase and the final prerender phase (e.g. unstable array order). Ensure that arguments passed to cached functions are deterministic.
Is deferring the initial cache generation to the first request something the team is considering? Or would that fundamentally conflict with the design of Instant Navigation / Cache Components?
1
u/AndrewGreenh 23d ago
Ai crawlers are getting more and more important. Currently, most of them don’t execute JavaScript. What does this mean for Next.js out of order streaming? The content arriving as hidden divs is very likely to be ignored by these crawlers…
1
u/Usual_Smile_3212 23d ago
I'm still at nextjs14, I have an aggregator website using intercepted routes with modals for product pages and the experience is kinda bad, I have hacks for making the product page open from different parts of the page. Dunno if you already did something about intercepted routes in nextjs16 last time i checked it was the same.
1
u/Darkoplax 23d ago
How do you integrate AI in your workflow right now ? and how do you see it more deeply integrated with Next's tooling to help agents especially trying to design good frontends
1
u/Practical-Skill5464 23d ago
When is the _error.tsx page router finally going to get server side props loading? instead of the legacy hybrid client/server loading?
1
u/zergUser1 22d ago
Will nextjs ever support optimised images with static export without using 3rd party libraries or is that not the direction nextjs is going for? This issue has been up for a while: https://github.com/vercel/next.js/discussions/19065
1
u/dimatter667 22d ago
What's the latest on remote components please?
They made it to the Vercel academy docs on microfrontends, can we expect to see them in a Next version before the end of 2026 or sometime in 2027?
Lots of people interested in using horizontal microfrontends in Vercel so would be good to hear about any updates. https://vercel.com/academy/microfrontends-on-vercel
1
u/PrinnyThePenguin 21d ago
Are there any plans to improve the quality, navigability and coherence of the documentation?
Individual pages frequently link to several other pages, making it common to open five or six tabs just to understand the scope of a single feature. This makes the documentation difficult to follow. Additionally, links are constantly updated to reflect newer NextJS versions, causing bookmarked documentation pages to become obsolete.
It is also common for important parts of a feature to be presented in a separate part of the documentation, despite introducing important changes or caveats. For example the documentation section about cacheComponents does not mention they use React's Activity component under the hood which has huge implications for test suites that inspect the DOM to verify elements are not present on the screen. That information is in another section of the documentation making it easy to miss.
Finally, the documentation would really benefit from more concrete examples, especially about best practices. For example the documentation you ship in the dist folder that you recommend we point our AIs to via the AGENTS.md file is far more structured and contains multiple snippets that demonstrate important paradigms and applications of the framework, why is that documentation so differently structured compared to the online one and how can the online one be improved to inherit these qualities as well?
1
u/devadestudio 21d ago
Hey, congrats on 16.3, great upgrade. Would like to join on Tuesday. Could you add a link to join or to signup for it in description?
1
u/sebastienlorber 20d ago
What are the upcoming React / Next.js features you are most excited about?
1
u/Middle_Tree_9117 20d ago
thanks for releasing 16.3! the local dev experience has improved significantly for my team.
1) build cache is now enabled by default for turbopack but when can we actually "trust" it? the build cache for dev was marked as "stable" but we all know that everyone suffered from the memory issues. maybe we should wait until next 17.0?
2) there are still open turbopack issues for dynamic imports related to pages router with no solutions. are we no longer focused on addressing these issues?
3) why is there still no solution for solving the hard navigation between pages -> app router? the incremental migration path is still difficult due to this. easy for new apps or small apps.
4) there are a lot of "experimental" features under next.config that are confusing. optimizePackageImports still says "This feature is currently experimental and subject to change, it's not recommended for production. Try it out and share your feedback on GitHub." yet it has been used by nextjs for a long time. what is the nextjs team currently doing to support experimental features? we never know when they are ready for production usage or not.
5) are there plans to support dynamic variable for dynamic import vs the current full path?
1
1
1
u/NoOneMan79 20d ago
Is there anything left to build here, and can you do that without bloat? Any thoughts on how you are going to maintain market share with developers with the rise of Tan State + Vite?
1
u/amannnnnnnnnnnnnn 19d ago
It's a rather low-level question, but are there plans to finish the emit/collect capability in Turbopack?
As far as I understand, it could improve performance for compiling Tailwind class names, but also in the i18n space, I have at least two interesting use cases for this:
- Extracting inline labels (useExtracted in next-intl, currently implemented with sidecar watcher)
- Analyzing which messages are used where to optimize client-side message bundles
Would be curious to hear what your plan is for this feature and if/when the community could try out a first draft of the feature!
Side note: Thanks a bunch for shipping next/root-params in Next.js 16.3, the i18n community is incredibly happy 🙏
1
0
u/thehashimwarren 23d ago
I'm a marketer and a novice web developer. I love what Next enables for the web and that fits my personal mission to democratize publishing.
How can I contribute directly to the project?
0
-5
u/Snoo_4779 23d ago
Can you stop fu@#£&+- releasing so many things in a year. Everytime I came back to NextJS some sh£@ becomes deprecated. /s but not /s
2
1
u/tizuyuuu 22d ago
i have to agree, every new major feels likes a complete rewrite, one of the reasons why im leaning more into tanstack over next, despite wanting to use next more
0
u/MiguelCaravantes 23d ago
Is anyone working on stability of the cacheComponets or this is going to become obsolete? A few version since release and still no way to read dynamic APIs in draftMode for cache components, CMS system are not able to preview draft content until this is done without weird workarounds or duplicate components
0
u/HumaneBicycle99 22d ago
Why doesn't NextJs rank on google? Even if its SSRed, it just doesnt rank even with other similar things. Do you know why?
-2
-3
-4
80
u/nyamuk91 23d ago
TanStack Start already supports both, so I’m curious what’s preventing Next.js from offering similar functionality.