fix(nextjs): Don't use chalk in turbopack config file #17806
Merged
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.
We don't know yet why but this config code seems to be evaluated once at runtime for some users when using turbopack. The chalk import breaks with
Failed to load external module @sentry/nextjs: Error [ERR_REQUIRE_ESM]
.Just getting rid of this import for now to not break apps.
We're still investigating together with Vercel why this this code gets pulled in.
closes #17691
Note
Removes the chalk import and replaces the colored debug message with a plain "[@sentry/nextjs]"-prefixed string in Turbopack rule handling.
chalk
import frompackages/nextjs/src/config/turbopack/constructTurbopackConfig.ts
.chalk
-based coloreddebug.log
with a plain"[@sentry/nextjs] - ..."
message insafelyAddTurbopackRule
.Written by Cursor Bugbot for commit 9026ac4. This will update automatically on new commits. Configure here.