Skip to content

fix(nextjs): Don't use chalk in turbopack config file #17806

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 29, 2025
Merged

fix(nextjs): Don't use chalk in turbopack config file #17806

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions packages/nextjs/src/config/turbopack/constructTurbopackConfig.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
import { debug } from '@sentry/core';
import * as chalk from 'chalk';
import type { RouteManifest } from '../manifest/types';
import type { NextConfigObject, TurbopackMatcherWithRule, TurbopackOptions } from '../types';
import { generateValueInjectionRules } from './generateValueInjectionRules';
Expand Down Expand Up @@ -57,9 +56,7 @@ export function safelyAddTurbopackRule(
// If the rule already exists, we don't want to mess with it.
if (existingRules[matcher]) {
debug.log(
`${chalk.cyan(
'info',
)} - Turbopack rule already exists for ${matcher}. Please remove it from your Next.js config in order for Sentry to work properly.`,
`[@sentry/nextjs] - Turbopack rule already exists for ${matcher}. Please remove it from your Next.js config in order for Sentry to work properly.`,
);
return existingRules;
}
Expand Down
Loading