Decouple webpack config for development and production build about chrome-extension-webpack-boilerplate HOT 2 CLOSED

This separation for this boilerplate is really worth? Just place the production compile configs in webpack.config.js doesn't do the work?

I didn't included uglify and code minimization by default because I don't think that these things are critically necessary to an extension, where these assets won't be loaded from the network, and the extension is downloaded from Chrome Store compressed.

Don't take me wrong, I just want to keep this boilerplate as minimal possible to make sure that it is a comprehensive example how to start a Chrome extension with Webpack, the focus isn't to create the most complete boilerplate. Right now there are things already added that I want to remove to keep it even more simple.

About the CSS, I didn't analyze your PR yet, but is critical to include all CS in a single file? But I agree that the CSS must be separated from the javascript bundle because screen flickering, but we discuss this on the PR.

from chrome-extension-webpack-boilerplate.

Closing by the lack of activity.

from chrome-extension-webpack-boilerplate.