Threshold‑Based Performance Hints vs Silent Builds: Which Keeps Noise Low?

Goal

Reduce console noise from Webpack’s performance hints while still catching genuine bundle size regressions.

Constraints

Default thresholds (250 kB assets, 400 kB entrypoints) often trigger warnings for legitimate large files, especially in multi‑entry or source‑map‑heavy builds.

Disabling hints removes all feedback, risking unnoticed regressions.

Unresolved Decision

Should we fine‑tune thresholds, use per‑chunk overrides, or accept a silent build to balance noise and safety?

Specific Questions

• What threshold values are appropriate for a typical multi‑entry project to avoid false positives?
• Does the per‑chunk‑type hint feature provide a cleaner solution for silencing image or font warnings while keeping JS size alerts?
• Is turning performance.hints off a viable long‑term strategy if we rely on other tools to monitor bundle growth?