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
Support Babel 6 #47
Comments
What is the Babylon version you are using here? This rather seems to be a configuration error or an inconsistent state of your nodes_module folder. Sure, we could upgrade to a newer version of Babylon, but that shouldn't be necessary. Whatever Babel version you are using shouldn't impact react-docgen and vice versa. |
That's what I though, I'm gonna investigate more on this.
I'm using the latest release of react-docgen. I'm not using directly babylon. |
@fkling Thanks for your help! It was indend an issue with my dependences. I had two version of babylon (v5, v6), and my webpack config wasn't resolving the good one 😁. |
Is there any ETA for the Babel 6 upgrade? I am running into the same issue and ideally I'd rather avoid playing with module resolution in web pack. |
@yrashk: There is no plan to upgrade babylon atm. Can you share information about your setup? You have to think of However, there could be an issue when npm didn't install the correct dependencies. I guess one solution to avoid these issues could be to use |
Experiencing something similar to this... I can run
As @oliviertassinari described originally, the I've tried upgrading all my |
react-docgen@v2 uses babylon 5 and that will not change. We also have a beta version v3.0.0 which uses babylon 7, you can try that. |
@danez Material-UI has been relying on the v3.0.0 beta for months now. It's working great. |
@danez tried |
just install with npm the latest beta
Installing the branch directly won't work, as there are build steps involved when releasing. |
When using this module with a source code that is using babel 6.
I'm having this error:
This is from
webpack:///./~/babylon/lib/parser/index.js
:I guess that upgrading the version of babylon would solve the issue.
The text was updated successfully, but these errors were encountered: