Skip to content

Conversation

sebmarkbage
Copy link
Collaborator

Babylon 6.12.0 is broken. (Maybe related to babel/babel-eslint#280 )

I couldn't figure out how to do this using package configuration alone so I ended up just manually hacking the yarn.lock file to force a downgrade of babylon to 6.8.0 since otherwise it gets resolved to 6.12.0 which is broken.

@chicoxyzzy
Copy link
Contributor

Related Yarn issue yarnpkg/yarn#1158

version "6.11.5"
resolved "https://registry.npmjs.org/babylon/-/babylon-6.11.5.tgz#35cce8fb5f98353931d275cb56871fbf17bf9a00"
babylon@6.8.0:
babylon@^6.0.18, babylon@^6.11.0, babylon@^6.8.1, babylon@6.8.0:
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the hack. The rest are just regular updates.

I couldn't figure out how to do this yarn alone so I ended up
just manually hacking the yarn to force a downgrade of babylon
to 6.8.0 since otherwise it gets resolved to 6.12.0 which is
broken.
@sebmarkbage sebmarkbage merged commit 4132cc4 into facebook:master Oct 20, 2016
@hzoo
Copy link
Contributor

hzoo commented Oct 22, 2016

@sebmarkbage What's the issue with babylonv6.12.0? Feel free to ping me on related Babel issues or file an issue in babylon

acusti pushed a commit to brandcast/react that referenced this pull request Mar 15, 2017
I couldn't figure out how to do this yarn alone so I ended up
just manually hacking the yarn to force a downgrade of babylon
to 6.8.0 since otherwise it gets resolved to 6.12.0 which is
broken.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants