Repository navigation
test(nextjs): Bump nextjs-16 E2E app to Next.js 16.4.2 - #25686
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
size-limit report 📦Compared: 274cc2d (PR test merge using develop at a4cf21f) Against: a4cf21f (develop) · base run #63265 ✅ Baseline matches: this diff contains only this PR's changes.
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Optional E2E testsAll optional checks were successful. 31 successful. See the run. Successful checks
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Next.js 16.3.8 drops a client component from the client reference manifest when webpack gives its concatenated module the id 0, because it checks the id for truthiness. The deterministic module ids depend on the module identifiers, which include the pnpm directory names of the loaders. Since webpack 5.112.1 was published, the peer suffix of @sentry/nextjs changed and `app/global-error.tsx` got the id 0 on CI, so prerendering failed. Next.js 16.4.0 fixed the check (vercel/next.js#97936). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mydea
changed the title
andreiborza
approved these changes
Oct 23, 2026
mydea
marked this pull request as ready for review
October 23, 2026 09:11
s1gr1d
pushed a commit
that referenced
this pull request
Oct 23, 2026
The `nextjs-16 (webpack)` E2E job fails on every branch because prerendering throws `Could not find the module ".../app/global-error.tsx#default" in the React Client Manifest`. That comes from a bug in Next.js 16.3.8: its client reference manifest plugin skips a client component whose webpack concatenated module got the id `0`, because it checks the id for truthiness. Next.js fixed this in 16.4.0 (vercel/next.js#97936), so this bumps the app's pinned `next` to 16.4.2. 16.3.8 is the last 16.3 release, so there's no 16.3 patch to pin to instead. Production module ids are deterministic hashes of the module identifiers, and those include the pnpm directory names of the loaders. The job started failing on the same develop commit that had passed a few hours earlier. The only dependency in the lockfile published in between is webpack 5.112.1, which changes the peer suffix in the `@sentry/nextjs` directory name. That's very likely what moved `app/global-error.tsx` to id `0` on CI. Locally the paths differ, so the ids differ too. Forcing the id to `0` reproduces the failure on 16.3.8, and the same build passes on 16.4.2. The `latest` webpack variant already runs 16.4.x and kept passing. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 6df508e)
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.
The
nextjs-16 (webpack)E2E job fails on every branch because prerendering throwsCould not find the module ".../app/global-error.tsx#default" in the React Client Manifest. That comes from a bug in Next.js 16.3.8: its client reference manifest plugin skips a client component whose webpack concatenated module got the id0, because it checks the id for truthiness. Next.js fixed this in 16.4.0 (vercel/next.js#97936), so this bumps the app's pinnednextto 16.4.2. 16.3.8 is the last 16.3 release, so there's no 16.3 patch to pin to instead.Production module ids are deterministic hashes of the module identifiers, and those include the pnpm directory names of the loaders. The job started failing on the same develop commit that had passed a few hours earlier. The only dependency in the lockfile published in between is webpack 5.112.1, which changes the peer suffix in the
@sentry/nextjsdirectory name. That's very likely what movedapp/global-error.tsxto id0on CI. Locally the paths differ, so the ids differ too. Forcing the id to0reproduces the failure on 16.3.8, and the same build passes on 16.4.2. Thelatestwebpack variant already runs 16.4.x and kept passing.🤖 Generated with Claude Code