We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We see people using our webpack config by including it, and we even document it. @storybook/react/dist/server/config/webpack.config
@storybook/react/dist/server/config/webpack.config
But reaching deep into a package is a bad practice, because it's fragile, and makes it harder for us to refactor.
We should publish the default webpack config as it's own package.
The text was updated successfully, but these errors were encountered:
Just a thought, but what about having it as a named export?
import { webpackConfig } from "@storybook/react"
Sorry, something went wrong.
yeah valid point, that's an option too!
Care to make this into a PR @heinzmuller ?
We found a better solution where the default is passed as a parameter in full control mode.
No branches or pull requests
We see people using our webpack config by including it, and we even document it.
@storybook/react/dist/server/config/webpack.config
But reaching deep into a package is a bad practice, because it's fragile, and makes it harder for us to refactor.
We should publish the default webpack config as it's own package.
The text was updated successfully, but these errors were encountered: