Added the ability to pass more webpack.config options

[BowlingX]

To support loader configurations (mentioned in #40), I made adjustments to support additional configuration properties.

[arunoda]

Actually, this is not what we should do. It's not possible to extend like this since it'll replace our configurations. But I mention is we can import his main webpack config into the webpack config in .storybook directory and get any modules he use.

[arunoda]

Currently we only support loaders and plugins. But, if we need something else we can specifically look at it.
This kind of thing will break our app.

BTW: Thanks a lot for the PR.

[BowlingX]

I removed the plugins and loader configurations from customConfig before, I could also remove the rest that is used by the application (or we assign it the other way around). The Problem is, that some plugins (like postcss-loader) require to be configured in the main configuration.

[arunoda]

Could you show me the sample webpack config for postcss-loader. Then we can try to do something.

[BowlingX]

Sure :)

taken from the examples:

var precss       = require('precss');
var autoprefixer = require('autoprefixer');

module.exports = {
    module: {
        loaders: [
            {
                test:   /\.css$/,
                loader: "style-loader!css-loader!postcss-loader"
            }
        ]
    },
    postcss: function () {
        return [precss, autoprefixer];
    }
}

[arunoda]

Thanks.
I moved the discussion to here: #46

We can discuss there.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 06f6d68. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx run-many -t build -c production --parallel=3

---

Sent with 💌 from NxCloud.