-
Notifications
You must be signed in to change notification settings - Fork 1
FIX babel-core including react-display-name & UPGRADE babel & other packages #3
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
Conversation
UPGRADE to babel:6.x.x UPGRADE to lodash:4.x.x UPDATE webpack UPDATE glob
Thanks for the PR, I'll try to check it today! |
I started testing your changes with SourceJS react bundle example here in
Does changes to plugin require some changes to project as well? |
Unfortunately, yes: You need a new .babelrc in your project folder:
|
I'm not sure if there's a way around that with the 'npm dependency install'-route. But I think it's actually correct to have a .babelrc there. |
That totally makes sense, since they decoupled the babel config from the project code. I will continue the testing. |
I've made the bundle working in |
Does using this .babelrc make it work?
This is exactly what the plugin itself uses. |
I've tested with new presets, now it's working fine, will merge it and release with breaking change version. Thanks again for your PR! |
Super awesome! Happy to help! |
At first i just wanted to see if I could fix a small problem I had with a package
react-display-name
being loaded twice. See styleguidist/react-styleguidist@596c42dThen I thought what the hell, let's try upgrade to babel 6; as that's what I've wanted to do for a while.
Found a merge PR for react-styleguidist for doing just that, here and pretty much followed that and fixed the stuff that came up.