Fix loader concatentation bug#173
Conversation
|
I need more information. I can't see what this solves anything. This change seems to have no effect on anything. Am I wrong? |
|
If I have a custom webpack config that looks like this, it'll break: I can fix it, by changing it to this: Take a look at these lines: https://github.com/kadirahq/react-storybook/blob/master/src/server/config.js#L90-L93 If |
|
Okay. I got it. return {
...customConfig,
// We'll always load our configurations after the custom config.
// So, we'll always load the stuff we need.
...config,
// We need to use our and custom plugins.
plugins: [
...config.plugins,
...customConfig.plugins || [],
],
module: {
...config.module,
// We need to use our and custom loaders.
...customConfig.module || {},
loaders: [
...config.module.loaders,
...customConfig.module? customConfig.module.loaders || [] : {},
],
},
};Isn't it? |
|
I think instead of |
|
@stefvhuynh Your PR sounds great. I'll do a release within today. |
|
View your CI Pipeline Execution ↗ for commit 01f687d
☁️ Nx Cloud last updated this comment at |
This has to do with using custom
webpack.config.jsfiles. The code tries to addcustomConfig.module.loaders. And ifcustomConfig.moduleis not defined, there is an error.