fix(nextjs): Apply silent to the SDK's own build logs - #23621
Merged
Conversation
…logs `silent` was only forwarded to the bundler plugin, so every message the Next.js SDK printed itself still reached the console despite the option being documented as suppressing all Sentry SDK build logs. Route those messages through a small `silent`-aware logger and thread the option to the helpers that log but did not previously receive it. The removed-option warning goes through the existing `logWarning` hook of `warnOnRemovedBuildOptions`, so no core change is needed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
size-limit report 📦
|
The loaders are their own rollup entry point built with `preserveModules`, so emitted paths are relative to the module graph's common root. Importing the shared build logger from `src/config` moved that root up one level and emitted every loader into `config/loaders/loaders/`, so the `path.resolve(__dirname, 'loaders', ...)` lookups in `webpack.ts` no longer resolved and every Next.js app failed to compile. Check `silent` inline in the loader instead, and document the constraint so the import is not reintroduced. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Member
Author
|
bugbot run |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 666aa7f. Configure here.
chargome
marked this pull request as ready for review
August 26, 2026 09:43
chargome
requested review from
andreiborza,
logaretm,
mydea,
nicohrubec and
s1gr1d
and removed request for
a team and
mydea
August 26, 2026 09:43
nicohrubec
approved these changes
Aug 26, 2026
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
3 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.
Routes the SDK's own build-time output through a
silent-aware logger, sosilent: truesuppresses it as documented.silentinto the build helpers that log but didn't receive it, matching howdebugis already passedsilentalso suppresses the "could not inject SDK init" error, matching the bundler plugin's logger, which gateserroronsilenttoowarnOnRemovedBuildOptionsneeded no core change — it already accepts alogWarningcallbackFixes #23620