You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The latest Next.js@10 version was released 3 years ago and has about 10k weekly downloads (I pulled this number during Christmas week so actual is probably 3-4x). For comparison, Next.js has about 5mil downloads on regular weeks.
The latest Next.js@11 version was released 2 years ago and has about 10k weekly downloads (also pulled this number during Christmas so actual is likely 3-4x). The most used version I can spot has about 30k/wk.
Next.js 11 came with webpack 5 support but still supports webpack 4
Next.js 12 removed webpack 4 support
Dropping version 10 is a no-brainer in my opinion, but we don't gain a lot from it. Dropping version 11 is a bit more debatable but would allow us to drop webpack 4 support which will allow us to simplify build time logic and drastically reduce the complexity of our test infra.
Update: We may have a plan to use @vercel/otel to instrument performance in Next.js. This would require us to bump the minimum Next.js version to at least 13.
I think I have settled on this topic. Because we will rely heavily on OpenTelemetry going forward, we should use the first Next.js version that also supports OTel.
I have found the following PR in the Next.js repository: vercel/next.js#46198, which adds some OTel instrumentation to Next.js. This change was first included in version 13.2.0 of Next.js.
Because of the above, I would vote that we make 13.2.0 the minimum version compatible with Next.js.
Activity
mydea commentedon Dec 14, 2023
@lforst can you evaluate this when you find some time?
lforst commentedon Jan 2, 2024
Some facts:
Dropping version 10 is a no-brainer in my opinion, but we don't gain a lot from it. Dropping version 11 is a bit more debatable but would allow us to drop webpack 4 support which will allow us to simplify build time logic and drastically reduce the complexity of our test infra.
No decision yet.
feat(v8): Bump minimum Node Version to 14 (#10527)
lforst commentedon Feb 12, 2024
Update: We may have a plan to use
@vercel/otelto instrument performance in Next.js. This would require us to bump the minimum Next.js version to at least 13.lforst commentedon Mar 14, 2024
I think I have settled on this topic. Because we will rely heavily on OpenTelemetry going forward, we should use the first Next.js version that also supports OTel.
I have found the following PR in the Next.js repository: vercel/next.js#46198, which adds some OTel instrumentation to Next.js. This change was first included in version
13.2.0of Next.js.Because of the above, I would vote that we make
13.2.0the minimum version compatible with Next.js.mydea commentedon Mar 14, 2024
Sounds reasonable to me! But let's double check this with folks, to be on the safe side.
AbhiPrasad commentedon Mar 19, 2024
Closing because we've picked
13.2.0as per #11097