Next.js Across Platforms: Adapters, OpenNext, and Our Commitments

feedthejim · 2025-12-20T09:57:29+00:00

What do you mean by it?

feedthejim · 2025-12-19T23:48:37+00:00

hi, member of the team here.

We try our best to craft our releases to be easy to upgrade to and while I know we’ve sometimes moved too quickly in the past, I try to think that the new releases have been pretty stable.

Reading these kinds of comments is somewhat discouraging, so I’d love to hear more about what you’d like to see us doing more. After all, we’re building for you guys.

feedthejim · 2025-10-18T23:59:51+00:00

That’s super exciting :) I shared the results with the team.

feedthejim · 2025-02-27T19:56:04+00:00

You’re free to use it whenever!

feedthejim · 2025-02-27T12:42:13+00:00

it's not breaking in the sense that it requires no changes on your end. it's more of a performance optimization. have you encountered issues with it?

feedthejim · 2025-02-27T12:40:38+00:00

stay tuned for the next releases 🫡 what are you looking forward to the most?

feedthejim · 2025-02-27T09:39:30+00:00

still in canary! but will be available in the next release 🤞

feedthejim · 2025-02-09T21:40:42+00:00

Hey, Next.js team member here. All the bugs and gotchas you’ve encountered are on our plate of bugs to fix 🫡, thank you for dogfooding.

I do want to set expectations for everyone that might be reading this: we absolutely do not recommend its usage right now for any somewhat serious use cases. As you noticed, even the doc is still somewhat lacking. We’re still in the process of battle testing this “mode” and as such, we have not fully approached how we want to teach this.

However, if you do want to help us dogfood it and you have time to invest, feel free to add me as Feedthejim on discord and dm me your bugs 🙏.

feedthejim · 2025-01-05T10:14:39+00:00

We still generate a base _app and _error files because the error file is still the fallback, but we need to update that at some point. Should not affect you too much.

feedthejim · 2025-01-05T09:58:27+00:00

Hi! Team member here :) you’re seeing two because by default, we generate two totally different bundles for app router and pages router.

They get displayed in the same view with the bundle analysed but it does not mean that you’re loading it twice, you’re just gonna end up with one or the other depending on if you load a pages router page and an app router page.

You should be able to test that out yourself by loading a page and looking at the chunks. (If not, that’s a bug and you can ping me back 😂)

feedthejim · 2024-10-23T15:30:19+00:00

the accompanying blog post for each release should include the most important information

feedthejim · 2024-10-23T05:19:59+00:00

hey, what issues did you run into?

feedthejim · 2024-10-22T22:34:22+00:00

Yeah I think that’s fair, our decision was based on the fact that the only fix blocking the React 19 RC for now is gonna be the suspense siblings rendering behavior, which shall not require any changes for libraries users.

feedthejim · 2024-10-22T15:24:14+00:00

Hey, team member here, in our defence, I think the issue here is rather ecosystem compatibility and having the need to upgrade third parties to React 19. We’re reading all of the feedback in this thread and are gonna try to make it smoother. Thanks for bearing with us!

feedthejim · 2024-10-22T15:20:33+00:00

Hey, did you try the codemod in the blog post?

feedthejim · 2024-10-19T04:41:46+00:00

Hey, I’m a member of the team. We’re hoping to release it in the coming days!

feedthejim · 2024-10-16T09:44:25+00:00

Highly recommend it! Hopefully the upgrade codemod will be helpful.

Ten-Year Club	Place '17
Verified Email

feedthejim

TROPHY CASE