-
-
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
Custom babel config loading does not work #701
Comments
Can you paste both It looks like the code is behaving as it should, reading from If you're using the |
This should be working as intended. The only way to configure a custom |
I have been having problems getting this setup. I'm running a Rails 5.1 app, with two
The one in This is what my two files looked like:
{
"plugins": [
"transform-class-properties",
"transform-decorators-legacy",
"transform-function-bind",
"transform-object-rest-spread"
],
"presets": [
"env",
"react"
]
}
{
"plugins": [
"transform-class-properties",
"transform-decorators-legacy",
"transform-function-bind",
"transform-object-rest-spread",
[
"react-docgen",
{
"includeMethods": true,
"resolver": "findAllComponentDefinitions"
}
]
],
"presets": [
"env",
"react"
]
} If I copied the |
Do you have a custom webpack config @percyhanna ? If you do, can you paste the contents? |
Yes I do. The file itself is pretty bare, though, it's basically copying over Webpack config settings from the Rails app's |
Are you wondering what the |
You have to extend the webpack configs in a way that preserves our default settings or else it will default to the root https://storybook.js.org/configurations/custom-webpack-config/ |
I got
.babelrc
in root directory of my project and I want to override it for storybook as is said in docs (https://getstorybook.io/docs/react-storybook/configurations/custom-babel-config), but I can't do this.When I got
.babelrc
only in storybook config (.storybook/.babelrc
) , everything works fine.When I got
.bebelrc
in.storybook/.babelrc
and in root directory, storybook takes.babelrc
from root directory.node version: 7.5.0
npm version: 4.1.2
The text was updated successfully, but these errors were encountered: