[filipesilva]

This should help users send us profile logs for builds that take too long.

Blocked on #11488 due to webpack/webpack#7450.

[hansl]

This should use the new webpack/lib/debug/ProfilingPlugin instead of installing a new package.

[filipesilva]

It does both actually.

[hansl]

What does speed-measure-webpack-plugin does that ProfilingPlugin doesn't? I don't want to add an additional dependency if there's little to no benefit.

[filipesilva]

ProfilingPlugin gives you a chrome perf profile, while SpeedMeasurePlugin gives you total aggregated time per plugin and loader.

It's hard to get that overview with just ProfilingPlugin because the events not necessarily together.

Loaders, for instance, can have many tiny events all over the place, that can add up quickly.

The API to consume SpeedMeasurePlugin is also easier to parse so we can use it to automatocally track individual plugin and loader performance over time instead of just build time.

I think those are the main differences.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}