-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using exiting webpack config but still has default plugin CaseSensativePlugin #1069
Comments
by the way: how could i reuse our project's webpack config, and remove the default plugin? |
You can use your own config by putting it inside the I would recommend against it since you will be missing the entry points, outputs, and a few other things that make storybook work. The best way to go about it is to use the "full control mode" in the docs and import the configs from |
thank for your reply |
When in full-control mode you can remove the plugin you don't want, Can you post your custom |
This is my custom webpack.config.js, so i think storybook won't use default webpack.config.js anymore when i config my custom webpack.config.js, is this right? but seems it still use the default config CaseSensitivePathsPlugin, |
Thank you everyone, i had resolve this problem by use full-controll mode, it's my mistake that i thought when i wrote my custom webpack.config.js it will cover the default config. Actually it's not. |
sounds good! I'm going to close this issue then. |
Hi,
I use storybook in my project, and i reused our project's webpack config like below pic
but when i run yarn storybook, it shows below error message
Module not found: Error: [CaseSensitivePathsPlugin]
C:\Users`and i checked your default config under node_modules@kadira\storybook\dist\server\config\webpack.config.js
plugins: [new _webpack2.default.DefinePlugin((0, _utils.loadEnv)()), new _utils.OccurenceOrderPlugin(), new _webpack2.default.HotModuleReplacementPlugin(), new _caseSensitivePathsWebpackPlugin2.default(), new _WatchMissingNodeModulesPlugin2.default(_utils.nodeModulesPaths)],
i want to know why i used custom webpack config, it still use the default plugin?
The text was updated successfully, but these errors were encountered: