Skip to content

not compatible with babel-core 6.11.4 #1058

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

Closed
zaaack opened this issue Sep 30, 2016 · 4 comments
Closed

not compatible with babel-core 6.11.4 #1058

zaaack opened this issue Sep 30, 2016 · 4 comments

Comments

@zaaack
Copy link

zaaack commented Sep 30, 2016

I have babel-core ^6.11.4 installed in my project, and there were no error or warning when install ava, then I got this error when run async function demos in readme

npm test

> [email protected] test /Users/z/Projects/Electron/ELaunch
> ava


   1 exception


   1. Uncaught Exception
   Error: /Users/z/Projects/Electron/ELaunch/test/utils/test.js: You gave us a visitor
for the node type "ForAwaitStatement" but it's not a valid type
    at verify (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/node_modules
/babel-traverse/lib/visitors.js:224:13)
    at Object.explode (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/node
_modules/babel-traverse/lib/visitors.js:90:3)
    at traverse (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/node_modul
es/babel-traverse/lib/index.js:81:12)
    at NodePath.traverse (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/n
ode_modules/babel-traverse/lib/path/index.js:147:25)
at exports.default (/Users/z/Projects/Electron/ELaunch/node_modules/babel-helper-r
emap-async-to-generator/lib/index.js:10:8)
    at PluginPass.Function (/Users/z/Projects/Electron/ELaunch/node_modules/babel-plug
in-transform-async-to-generator/lib/index.js:13:56)
    at newFn (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/node_modules/
babel-traverse/lib/visitors.js:301:19)
    at NodePath._call (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/node
_modules/babel-traverse/lib/path/context.js:76:18)
    at NodePath.call (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/node_
modules/babel-traverse/lib/path/context.js:48:17)
    at NodePath.visit (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/node
_modules/babel-traverse/lib/path/context.js:106:12)
    at TraversalContext.visitQueue (/Users/z/Projects/Electron/ELaunch/node_modules/ba
bel-core/node_modules/babel-traverse/lib/context.js:167:16)
    at TraversalContext.visitMultiple (/Users/z/Projects/Electron/ELaunch/node_modules
/babel-core/node_modules/babel-traverse/lib/context.js:113:17)
    at TraversalContext.visit (/Users/z/Projects/Electron/ELaunch/node_modules/babel-c
ore/node_modules/babel-traverse/lib/context.js:209:19)
    at Function.traverse.node (/Users/z/Projects/Electron/ELaunch/node_modules/babel-c
ore/node_modules/babel-traverse/lib/index.js:161:17)
   at NodePath.visit (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/node
_modules/babel-traverse/lib/path/context.js:116:19)
    at TraversalContext.visitQueue (/Users/z/Projects/Electron/ELaunch/node_modules/ba
bel-core/node_modules/babel-traverse/lib/context.js:167:16)
    at TraversalContext.visitSingle (/Users/z/Projects/Electron/ELaunch/node_modules/b
abel-core/node_modules/babel-traverse/lib/context.js:118:19)
    at TraversalContext.visit (/Users/z/Projects/Electron/ELaunch/node_modules/babel-c
ore/node_modules/babel-traverse/lib/context.js:211:19)
    at Function.traverse.node (/Users/z/Projects/Electron/ELaunch/node_modules/babel-c
ore/node_modules/babel-traverse/lib/index.js:161:17)
    at traverse (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/node_modul
es/babel-traverse/lib/index.js:83:12)
    at File.transform (/Users/z/Projects/Electron/ELaunch/node_modules/babel-core/lib/
transformation/file/index.js:548:35)
    at /Users/z/Projects/Electron/ELaunch/node_modules/babel-core/lib/transformation/p
ipeline.js:50:19

It turns out the problem is the babel-core version, after I set it to ^6.3.21, the error disappered.

@vinz243
Copy link

vinz243 commented Oct 1, 2016

Wow thanks a lot. This solved my issue would have never foind out otherwise :)

@zaaack
Copy link
Author

zaaack commented Oct 1, 2016

@vinz243 It tooks me a lot of time too because there were not much information in google, you are welcome :-)

@morenoh149
Copy link

this is odd. You had to roll back to a previous version?

@novemberborn
Copy link
Member

this is odd. You had to roll back to a previous version?

I imagine it installed a newer, non-broken version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants