feat(nextjs): Prepare for next 16 bundler default #17868
Merged
Conversation
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
size-limit report 📦
|
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
JPeer264
approved these changes
Oct 13, 2025
dev-packages/e2e-tests/test-applications/nextjs-app-dir/tests/transactions.test.ts
Show resolved
Hide resolved
dev-packages/e2e-tests/test-applications/nextjs-app-dir/playwright.config.mjs
Show resolved
Hide resolved
logaretm
approved these changes
Oct 13, 2025
andreiborza
pushed a commit
to thedanchez/sentry-javascript
that referenced
this pull request
Oct 15, 2025
Next.js will switch the default bundler starting with Next.js v16 - Updated detection logic for turbopack vs webpack - Updated generic tests (app dir + pages dir) to only run on webpack (we'll need to update these as soon as next16 is released) (there are tests that won't pass on turbopack and keeping this in sync for both bundlers will become unmaintainable) - Add a bunch of unit tests - Disabled `next dev --webpack` tests for now as instrumentation breaks – tracked in [linear](https://linear.app/getsentry/issue/FE-618/webpack-breaks-instrumentation-for-dev-mode-in-next-16) - Middleware tests failing likely due to missing [Proxy support ](getsentry#17894), will split this up in a follow up pr
kevva
reviewed
Oct 20, 2025
Comment on lines
+114
to
+132
| export function detectActiveBundler(nextJsVersion: string | undefined): 'turbopack' | 'webpack' | undefined { | ||
| if (process.env.TURBOPACK || process.argv.includes('--turbo')) { | ||
| return 'turbopack'; | ||
| } | ||
|
|
||
| // Explicit opt-in to webpack via --webpack flag | ||
| if (process.argv.includes('--webpack')) { | ||
| return 'webpack'; | ||
| } | ||
|
|
||
| // Fallback to version-based default behavior | ||
| if (nextJsVersion) { | ||
| const turbopackIsDefault = isTurbopackDefaultForVersion(nextJsVersion); | ||
| return turbopackIsDefault ? 'turbopack' : 'webpack'; | ||
| } | ||
|
|
||
| // Unlikely but at this point, we just assume webpack for older behavior | ||
| return 'webpack'; | ||
| } |
There was a problem hiding this comment.
@chargome, this is incorrectly returning turbopack for me. I'm running Next.js with Rspack and had to do some shenanigans to make it work after they changed the default bundler to Turbopack. So what I'm running is this:
NEXT_RSPACK=true next dev
NEXT_RSPACK=true next build
NEXT_RSPACK=true next start
I noticed our source maps stopped working in 10.20.0 and narrowed it down to this.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Next.js will switch the default bundler starting with Next.js v16
next dev --webpacktests for now as instrumentation breaks – tracked in linearcloses https://linear.app/getsentry/issue/FE-617/support-new-default-bundling-behaviour-for-nextjs-16