Repository navigation
⬆️ chore: Upgrade Next.js to 16.4.0 - #807
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Contributor
📦 Next.js Bundle Analysis for librechat.aiThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This branch was successfully deployed
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
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.
Summary
Bumps
nextfrom 16.2.12 to 16.4.0 (exact pin, as before). The lockfile also picks up the transitive updates that come with it (sharp,postcss,semver,nanoid).next-env.d.tsgains theroot-params.d.tsimport that Next 16.4 generates on build.Cache Components is not enabled here. It is a separate migration and is not needed for this upgrade.
Testing
pnpm install: exit 0,nextresolves to 16.4.0pnpm build(webpack): exit 0, no warnings or deprecations in the outputpnpm typecheck: exit 0pnpm test: 404 tests in 34 files passedpnpm lint: exit 0Not checked: pages, MDX rendering, search and i18n routes in a browser, the Playwright e2e suite, and bundle size. For reference, one
pnpm buildtook about 3m55s on 16.2.12 and 4m54s on 16.4.0 on a shared machine, so build time is not improved on this setup.