taskr: ES6 syntax failing in 0.3.4

When trying to test the quickstart guide against 0.3.4 I found that fly is now throwing an error when running or query tasks from a Flyfile with ES6 syntax.

Fly failing on ES6

stack: 
  - ~/.dev/flytest/Flyfile.babel.js:1
  - (function (exports, require, module, __filename, __dirname) { export default f
  -                                                               ^^^^^^
  - SyntaxError: Unexpected token export
  -     at exports.runInThisContext (vm.js 73:16)
  -     at Module._compile (module.js 443:25)
  -     at Object.Module._extensions..js (module.js 478:10)
  -     at Module.load (module.js 355:32)
  -     at Function.Module._load (module.js 310:12)
  -     at Module.require (module.js 365:17)
  -     at require (module.js 384:17)
  -     at Object.list (~/.npm-packages/lib/node_modules/fly/dist/cli/list.js 28:14)
  -     at callee$0$0$ (~/.npm-packages/lib/node_modules/fly/dist/index.js 81:13)
  -     at tryCatch (~/.npm-packages/lib/node_modules/fly/node_modules/babel-runtime/regenerator/runtime.js 67:40)
message: 
  """
    ~/.dev/flytest/Flyfile.babel.js:1
    (function (exports, require, module, __filename, __dirname) { export default f
                                                                  ^^^^^^
    Unexpected token export
  """

This did not occur prior to 0.3.4 as far as I tested, and I am able to reproduce with a clean install of fly on my machine. This also does not occur when using ES5 syntax.

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Comments: 36 (14 by maintainers)

Most upvoted comments

I tried to reproduce this with a clean install, but I couldn’t. The currently listed deps seem OK too. I know this occurs when babel-core does not exist in your node_modules.