[Propostion] New API to instantiate plugin for diff supported output plugin

I really hate this code: https://github.com/mastilver/dynamic-cdn-webpack-plugin/blob/ba58d17d891a9e0db4d7dd2cca43f7b75ca8baa1/src/index.js#L51-L57

It’s working but for the user it can be very surprising and I don’t think it can be extended extensively to handle different output plugin (like #31 )

I think a better API would be to expose multiple constructor like (better name ?):

• DynamicCdnWebpackPlugin
• DynamicCdnWebpackPLuginForHtmlPlugin
• DynamicCdnWebpackPluginForAssetsPlugin
• …

DynamicCdnWebpackPLuginForHtmlPlugin would extend DynamicCdnWebpackPLugin and would override the output function

@aulisius What do you think? Do you have any other suggestion?

[aulisius]

The names are giving me Java nightmares O_O.

HtmlDynamicCdnWebpackPlugin

I’m cool with this because it’s the shortest but like is mentioning Webpack really necessary? The package name already has webpack on it, so we could drop Webpack in the constructor.

[aulisius]

I concur with the fact that we shouldn’t be exposing webpack internals to users. Cool, let’s go with the multiple classes approach then. I am okay with inheritance to a certain degree 😛