Check deps. which use old version of Tapable

[c0b41]

working great webpack 4 but some deprecated warning show up

[rubenspgcavalcante]

This error must be from other plugin you make use as I don't use Tapable in this plugin. 👍

[ClementVidal]

Using webpack 4.9.1, i confirm, that as soon as you add the ChromeExtensionReloader plugin, you get this warning.
The corollary is also valid, as soon as you remove the ChromeExtensionReloader the warning goes away.

After trying to create a PR for that, it seams that several packages can cause this warning:

issue 701 in extract-text-webpack-plugin

issue 225 in copy-webpack-plugin

issue 154 in webpack-bundle-analyzer

I've forked this repo and upgraded the versions of those package but the warning is still there.
I guess there are other suspicious packages that could responsible of that ...

Need a bit more investigation

[rubenspgcavalcante]

Humm, there must be some tool to check dependencies deeply, so we can find anything is using old verions of Tapable. If there's not I'll try to do some script to read the package.json files inside node_modules 🤔

[ClementVidal]

I'm investigating on that.
I'll let you know if i found anything.

[ClementVidal]

I was wrong, this warning does not come from dependencies, but from the plugin itself:

The warning seams to come from the file ChromeExtensionLoad.ts:
The .plugin() call trigger the Warning.
The point is that compiler inherit from Tapable object.

apply(compiler) {
    if (process.env.NODE_ENV !== "production") {
      compiler.plugin("compilation", comp =>
        comp.plugin(
          "after-optimize-chunk-assets",
          chunks =>
            (comp.assets = {
              ...comp.assets,
              ...this._injector(comp.assets, chunks)
            })
        )
      );

      compiler.plugin("after-emit", (comp, done) =>
        this._triggerer()
          .then(done)
          .catch(done)
      );
    }
  }

[rubenspgcavalcante]

closed by #50

[c0b41]

@ClementVidal thanks

[rubenspgcavalcante]

Fix published in the 0.8.1 thanks to @ClementVidal 👍