-
-
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
Unknown option: direct.presets #13
Comments
Node 4.2.0 / NPM 3.8.1 |
Yes I think that's the issue. It's try to load babel5 inside this where we don't support. I'll see what I can do about this. |
I upgraded to Babel 6 and it works well. The bug is in Babel, and I couldn't figure out what was going wrong. It may be worth considering making babel v6 a peer dependency and call it good. |
Cool. I think that's something we can do. |
I think we can close this now. Since everybody is using babel6. |
Add android entry file for react native
Change styles a bit for much better look and feel.
…20.0 @kadira/storybook@2.20.0 untested⚠️
…20.1 @kadira/storybook@2.20.1 untested⚠️
Updated README to include sortStoriesByKind option
…20.0 @kadira/storybook@2.20.0 untested⚠️
If anyone Googles into here, I was getting a similar, but slightly different, error: ERROR in ./storybook/addons.js
Module build failed: ReferenceError: [BABEL] /Users/gerard/_work/crossroads-anywhere/react-native/storybook/addons.js: Unknown option: direct.presets
at Logger.error (/Users/gerard/_work/crossroads-anywhere/react-native/node_modules/babel-core/lib/transformation/file/logger.js:58:11)
├─┬ @storybook/cli@3.2.4
│ └─┬ jscodeshift@0.3.32
│ └── babel-core@5.8.38 It sounded like Babel 5 was the problem, so I had to explicitly install Babel 6: |
Thanks for posting your solution @hellogerard ! |
My project uses Babel 5. Following the setup example, I when I run
npm run storybook
, I get:It comes from the Webpack output. This error seems like a Babel 5/6 mismatch of some sort. Should Babel 6 be a peer dependency, or is this able to work with legacy Babel?
The text was updated successfully, but these errors were encountered: