Make it possible to get the generated webpack config for any command

[insin]

If you want to use https://github.com/benmosher/eslint-plugin-import, it has a Webpack resolver which needs the webpack config.

[ericclemmons]

Oh man, I hate that rule. I disable it wherever I can, since it causes a lot of duplication for it to work correctly between every single project :(

[insin]

Idea for this after looking at React Cosmos' integration docs - what if we added some modules under config/ with the name of the basic commands nwb supports which just generates the webpack config for that command (using nwb.config.js to determine the project type) and exports it?

Then integration with cosmos might look something like:

// cosmos.config.js
module.exports = {
  webpackConfigPath: 'nwb/config/serve',
  // ...
}