templates: bump templates to Next.js 16.2.0#16003
Merged
Merged
Conversation
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖 |
paulpopus
approved these changes
Mar 20, 2026
Contributor
|
🚀 This is included in version v3.80.0 |
TheBit
reviewed
Apr 15, 2026
| "cross-env": "^7.0.3", | ||
| "dotenv": "16.4.7", | ||
| "graphql": "^16.8.1", | ||
| "next": "15.4.11", |
There was a problem hiding this comment.
Hi @AlessioGr, why was with-cloudflare-d1 not bumped to 16.2.0? Was it a mistake, or is there any technical reason behind it? I'm using this template and trying to decide whether I should upgrade Next.js manually...
There was a problem hiding this comment.
@AlessioGr, have you had any chance to look at my question?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR bumps all our templates to use Next.js 16.2.0. As part of that process, we're renaming the next.config.mjs files to next.config.ts.