Shouldn't we use PROCESS_ASSETS_STAGE_ADDITIONAL instead of PROCESS_ASSETS_STAGE_ADDITIONS?

[slavafomin]

I was looking into the code of this plugin and found some discrepancy here:

copy-webpack-plugin/src/index.js

Lines 615 to 619 in dde71f0

	compilation.hooks.processAssets.tapAsync(
	{
	name: "copy-webpack-plugin",
	stage: compiler.webpack.Compilation.PROCESS_ASSETS_STAGE_ADDITIONS,
	},

The plugin uses the PROCESS_ASSETS_STAGE_ADDITIONS stage when tapping into the processAssets hook. However, this stage is described as the following in the docs:

PROCESS_ASSETS_STAGE_ADDITIONS - Add additional sections to the existing assets e.g. banner or initialization code.

Considering that the plugin copies individual files or entire directories and not adds additional sections to the existing assets shouldn't we use the PROCESS_ASSETS_STAGE_ADDITIONAL stage? It looks more appropriate for this use case:

PROCESS_ASSETS_STAGE_ADDITIONAL - Add additional assets to the compilation.

[alexander-akait]

Yep, you are right, we need switch on PROCESS_ASSETS_STAGE_ADDITIONAL

[alexander-akait]

Fixed #601