-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Allow full control over webpack config. #160
Conversation
Okay. Could you update the docs as well. |
Awesome thanks so much! Docs are added now! |
If a function is returned from the '.storybook/webpack.config.js' then it will kick in 'full-control mode'. The function accepts the baseConfig from storybook and the dev can modify it with full control. This is necessary for more custom webpack configurations.
Okay. This looks great. When we are releasing it, I'll take this. |
Thanks @arunoda! An estimate on timeframe for next release? |
Within this week. |
Will this allow full control over webpack.config.prod.js as well, or only webpack.config.js? |
This was not for prod only dev
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit d7c8c42. 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 targetSent with 💌 from NxCloud. |
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:
Example: