Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Does this Webpack 4 change mean the end of the plugin's current approach?
Is there another way to get a hold of the Webpack config being used after all the internal defaulting etc. has happened?
please make this plugin works with web pack 4 also,