You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to run webpack from the command line, the easiest way would be webpack --config ./webpack.build.js, for example. The --config argument expects an object to be passed back, and our webpack.make.js returns a function.
Was wondering if webpack.build.js, webpack.dev.js, and webpack.test.js are still needed. I didn't see where they are used (sorry if I missed it). The generated gulpfile.babel.js passes the options object to webpackCompile (in webpack.make.js) directly without using any of these files.
Is it possible these are an artifact from an earlier version or do they have another purpose?
The text was updated successfully, but these errors were encountered: