Skip to content
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

Pin babylon at 6.8.0 for ESLint to work #7008

Merged
merged 1 commit into from
Jun 9, 2016
Merged

Conversation

keyz
Copy link
Contributor

@keyz keyz commented Jun 9, 2016

babel/babylon#25 broke our linter (Error: Unknown node type TypeParameter.). Upgrading ESLint to 2.x would be the right way to go, but we can just pin babylon at 6.8.0 to do a quick fix.

CC @zpao @hzoo @kittens

@hzoo
Copy link
Contributor

hzoo commented Jun 9, 2016

I can do a patch release (in babel) to fix the unknown node type issue in a bit

edit: but now I'm not sure that it fixes this particular issue?

@keyz keyz merged commit 46cd6a0 into facebook:master Jun 9, 2016
@keyz
Copy link
Contributor Author

keyz commented Jun 9, 2016

@hzoo I tried upgrading ESLint to 2.x and that solved the issue, but we have quite a few custom rules here so it won't be an easy migration. I think it's fine to pin babylon at 6.8.0 for now. Thanks!

@keyz keyz deleted the fix-eslint branch June 9, 2016 23:19
@hzoo
Copy link
Contributor

hzoo commented Jun 9, 2016

Yeah there were a good amount of changes in 2.x. And FYI, when you do update to 2.x, update babel-eslint to 6.x too. Can check the gitter/ping me if help is needed

@keyz
Copy link
Contributor Author

keyz commented Jun 9, 2016

Thanks @hzoo! 😃

@zpao zpao added this to the 15-next milestone Jun 14, 2016
zpao pushed a commit that referenced this pull request Jun 14, 2016
@zpao zpao modified the milestones: 15-next, 15.2.0 Jun 14, 2016
@hzoo
Copy link
Contributor

hzoo commented Jun 28, 2016

This should be fixed now*

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.

4 participants