perf: next.config.ts build statistics plugin runs unconditionally

[nanaf6203-bit]

Summary

next.config.ts includes a BuildStatsPlugin that runs in production builds and may emit a .next/ analysis payload — overhead around 5%.

Affected area

next.config.ts, line ~145

Steps to reproduce

Inspect the plugin — console.log(stats) runs for every build.

Expected behaviour

Disable the plugin in production; enable only when ANALYZE=true.

Acceptance criteria

• Plugin gated by environment flag.
• Build logs are quiet without ANALYZE.
• Document the new behavior in README.

---

Filed automatically as part of the PropChain code-review sweep.

[chidumebiodoh123-cloud]

@chidumebiodoh123-cloud has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Can I work on this?

I have experience and I have reviewed the code. I will optimize the build configuration by ensuring the BuildStatsPlugin only runs when explicitly enabled for analysis builds. Scope: Update next.config.ts to conditionally register the plugin, eliminate unnecessary production build overhead, and preserve existing analysis functionality. Plan: Gate the plugin behind an environment flag, remove unconditional execution and logging, verify production builds remain unaffected, and ensure all acceptance criteria are fully covered.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @chidumebiodoh123-cloud to this issue.

[VeronicDev]

@VeronicDev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer please assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @VeronicDev to this issue.

[Mirabel64]

@Mirabel64 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello maintainer, can I work on this please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Mirabel64 to this issue.

[drips-wave]

Congratulations, @Mirabel64! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Mirabel64: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Mirabel64 as part of the Stellar Wave Program's 6th Wave 🥳

😎 @Mirabel64: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.