I'm using with copy-webpack-plugin 4.4.1 with webpack 4.0.0-beta.0 and I get this warning (although it seems to work since #211)
@bfred-it expected behavior, will be fixed in next major, after webpack@4 will be official release
This will stay for a while since the plugin needs to support webpack =< v4.0.0 and webpack 4 has a compat layer for the 'old' plugin system
@michael-ciniawsky in theory we can check on new api and use new api
This is handled by the compat layer in webpack imho. A option/flag to disable the warnings would be awesome, but this should also happen in webpack/webpack instead
@michael-ciniawsky --ignore-deprecation for webpack will be good
Yep, something like that or a sledgehammers --silent [...options] mode, since webpack can be quite noisy in general sometimes (e.g loader warnings per file/request) :)
Webpack 4 is now available.
Someone can send PR which feature detects webpack >= v4.0.0 via
const cb = (...args) => {}
...
if (compiler.hooks) {
const plugin = { name: 'CopyPlugin' }
compiler.hooks.someHook.tap(plugin, cb)
} else {
compiler.plugin('some-hook', cb)
}
Webpack 4 supported?
Let's do it in next patch. WIP
Released in v4.4.3 馃帀
I am getting this issue with version 4.6.0 and webpack 4.27.0.
Most helpful comment
I am getting this issue with version 4.6.0 and webpack 4.27.0.