All committers have signed the CLA.

@akx Do you still need this feature? I can write full roadmap for correct implementation

@akx Do you still need this feature? I can write full roadmap for correct implementation

Sure. This implementation seems to work though, it's just the npm audit snafus keeping it back. What's wrong with the implementation in your opinion?

@akx sorry, for delay, it should be solved on webpack side:

• we use webpack-sources for assets, so we need implement property stats() for https://github.com/webpack/webpack-sources/blob/master/lib/Source.js#L7
• emit stats from source here https://github.com/webpack/webpack/blob/master/lib/Compiler.js#L546 and write stats to saved file
• implement stats keeping here

In the future, it will also allow other plugins modify stats

@evilebottnawi

So... that means changes to both webpack-sources and webpack core itself, with the uncertainty of whether or not they'll get approved at all to begin with? Also, considering these are API changes, they'd probably be version-major?

If I rebase this PR, would it be approved until stats collection becomes (if it ever will be) implemented in Webpack itself?

We can't implement it on plugin side, we use compilation.hooks.additionalAssets hook, and on this hook assets do not exist yet on disk, they exit only on compilation.hooks.assetEmitted hook and on it we cannot modify assets, It’s also worth saying that we don’t know in what environment the webpack works, so fs module can't exists (I prepare a PR to use webpack input file-system for fast-glob so CopyWebpackPlugin can work in browsers without any problems). Therefore, this needs to be improved on the side of the webpack itself, and not the plugin.

We already had a discussion about this, and it was decided that the implementation on webpack-sources side it the best solution. Why we still haven’t done it? Because this is a rare request.

No need to be afraid to improve something.

they exit only on compilation.hooks.assetEmitted hook and on it we cannot modify assets

We're only modifying filesystem metadata that Webpack doesn't care about. That sounds like it should be safe.

, It’s also worth saying that we don’t know in what environment the webpack works, so fs module can't exists

The PR is aware of this and does a best effort to keep times: https://github.com/webpack-contrib/copy-webpack-plugin/pull/435/files#diff-2e0f2c5a9d0afaccd39535254a1c9076R1-R20

This implementation unsafe and potential break webpack-dev-server, solution is above

I guess I'll just close this...