fix: stats.hasWarnings() should respect ignoreWarnings

[nanianlisao]

Summary

Actually, I am not sure if this is a bug or if it was done intentionally. But I think hasWarnings in stats should respect ignoreWarnings。

Especially in the compiler.hooks.done hooks, stats obtained is directly processed via hasWarnings to handle warnings.

🤖 Generated by Copilot at 345939a

Refactor Stats.hasWarnings to use Compilation.getWarnings. This is part of a larger effort to optimize and enhance the stats output.

Details

stats.hasWarnings() should respect ignoreWarnings

🤖 Generated by Copilot at 345939a

• Refactor warnings handling logic in Compilation class (0,10,10,1,F0L3R

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: nanianlisao / name: chenxiang (2cf4283, 345939a, 6f8340a)

[webpack-bot]

For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

[nanianlisao]

@alexander-akait
Hi,
I've noticed that my pull request hasn't been reviewed yet. If you could find some time to review it, I'd really appreciate it.

Thanks a lot!

[alexander-akait]

I am fine with it, but I am afraid it can be a breaking change, because some tools can rely on this behaviour... I think we need a small dicussion here @webpack/core-support @webpack/cli-team

[snitin315]

@alexander-akait Yeah, this could be a potential breaking change. I believe we should consider this change for webpack v6

[vankop]

I think this is valid, ignoreWarnings should be respected.

[alexander-akait]

@vankop I think we need a test cases to prevent a regression in future

[alexander-akait]

Feel free to send it and we can merge it

[webpack-bot]

@nanianlisao Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@vankop Please review the new changes.

[nanianlisao]

Great, could you please take a look again. @alexander-akait