fix: Remove debug logging from webpack plugin#41
Merged
lightninglu10 merged 1 commit intomainfrom Nov 29, 2025
Merged
Conversation
Removes excessive console.log statements that clutter user build output: - Plugin initialization and options logging - Server/dev mode skip messages - Production mode entry message - TypeScript config path resolution logging - Alias detection and mapping logs These debug messages are unnecessary for end users and make build output noisy. Keeping console.warn statements for actual warnings that users should see (e.g., tsconfig parsing errors, missing main bundle). 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
❇️ CodePress Review Summary
👋 Hey team,
Overall the changes look great! No specific issues found.
Here's the quick rundown:
✅ Decision: APPROVE
The change removes only debug logging with no functional impact; risks are limited to reduced diagnosability and are non-blocking.
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
1 participant
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.
Summary
This PR removes excessive debug logging from the webpack plugin that clutters user build output. These console.log statements are only useful during plugin development and should not be shown to end users during their production builds.
Changes
Removed the following debug console.log statements:
[CodePress] Plugin apply() called with options:- Plugin initialization logging[CodePress] Skipping: isServer=true- Server build skip message[CodePress] Skipping: dev=true- Dev mode skip message[CodePress] Running in production mode, will build MODULE_MAP- Production mode entry message[CodePress] Looking for @ alias in tsconfig:- TypeScript config path logging[CodePress] Found paths block:- Path block detection logging[CodePress] Added alias from tsconfig:- Alias mapping logging[CodePress] No paths block found in tsconfig- Missing path block message[CodePress] Using default Next.js alias:- Default alias fallback messageWhat's Kept
All
console.warnstatements are preserved, as these show actual warnings that users should see:Impact
This change makes the webpack plugin much quieter during user builds, only showing warnings when something actually needs attention. The plugin will continue to function identically, just without the debug noise.
🤖 Generated with Claude Code