Allow full control over webpack config.

[timkindberg]

Because of very custom requirements on my project I will not be able to use storybook unless I can have more fine-grained control over the webpack config.

This pull request adds the 'full-control' features:

• If a function is returned from the '.storybook/webpack.config.js' then it will trigger 'full-control mode'.
• The function accepts the baseConfig from storybook and the dev can modify it with full control.
• The function must return a webpack config object.

Example:

// .storybook/webpack.config.js

// We will export a function instead of an object, the function will accept the base config
module.exports = (storybookBaseConfig) => {
  // Make whatever fine-grained changes you need
  delete storybookBaseConfig.module.loaders[0].exclude;

  // Return the altered config
  return storybookBaseConfig;
};

[arunoda]

Okay. Could you update the docs as well.
Here: https://github.com/kadirahq/react-storybook/blob/master/docs/configure_storybook.md#custom-webpack-configurations

[timkindberg]

Awesome thanks so much!

Docs are added now!

[arunoda]

Okay. This looks great.
We are working on some refactors in the mantra repo. (Unrelated to this PR)

When we are releasing it, I'll take this.

[timkindberg]

Thanks @arunoda! An estimate on timeframe for next release?

[arunoda]

Within this week.

[moroshko]

Will this allow full control over webpack.config.prod.js as well, or only webpack.config.js?
It would be great if we could control webpack.config.prod.js. For example: pass options to the uglifyjs plugin.

[timkindberg]

This was not for prod only dev
On Thu, May 5, 2016 at 7:23 AM Misha Moroshko notifications@github.com
wrote:

Will this allow full control over webpack.config.prod.js as well, or
only webpack.config.js?

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#160 (comment)

• Tim