lukeed / fly-esnext Goto Github PK

View Code? Open in Web Editor NEW

12.0 3.0 1.0 11 KB

Allow for ES6 and ES7 support throughout a Fly environment.

License: Other

JavaScript 100.00%

fly-esnext's Introduction

fly-esnext

Allows a flyfile.js to be written with new-age ES6 or ES7 syntax.

Install

npm install --save-dev fly-esnext

That's it! 🎉 You've now enabled async/await syntax for your flyfile.js!

Note: This will NOT compile your ES6 files into ES5. You must download and setup fly-babel for that.

Usage

A flyfile.js may also include require() statements (not shown).

// flyfile.js

export default async function () {
  await this.source('src/*.js') // etc...
}

export async function lint() {
  await this.source('src/*.js') // etc...
}

export async function styles(obj) {
  await this.source(obj.val || 'src/*.sass') // etc...
}

License

MIT © Luke Edwards

fly-esnext's People

Contributors

Stargazers

Watchers

Forkers

tjbenton

fly-esnext's Issues

Seems like right now, fly-esnext just replace some syntax constructions using regular expressions. It would be nice if it use babylon or uglify etc. to transfrom file AST, it will be more correct behavior for syntax transformations.

use async programatically

Is it possible to use this module to run programatically?

const fly = new Fly({
  plugins: [
    require('fly-typescript'),
    require('fly-clear'),
    require('fly-flatten'),
  ],

  tasks: {
    async default(fly) {
      yield fly.clear('dist');
      yield fly.source('server/templates/**/*')
        .flatten({ levels: 5 })
        .target('dist/server/templates');
    },
  }
})

await fly.start()

“TypeError: Cannot read property 'error' of undefined” when running: fly

Hello! I'm trying to run the following command:

$ ./node_modules/fly/cli.js -f flyfile.js

And I receive the following error:

stack: 
  - TypeError: Cannot read property 'error' of undefined
  -     at OptionManager.mergeOptions (~/Workspace/abc/node_modules/fly-esnext/node_modules/babel-core/lib/transformation/file/options/option-manager.js 126:28)
  -     at OptionManager.addConfig (~/Workspace/abc/node_modules/fly-esnext/node_modules/babel-core/lib/transformation/file/options/option-manager.js 107:10)
  -     at OptionManager.findConfigs (~/Workspace/abc/node_modules/fly-esnext/node_modules/babel-core/lib/transformation/file/options/option-manager.js 168:35)
  -     at OptionManager.init (~/Workspace/abc/node_modules/fly-esnext/node_modules/babel-core/lib/transformation/file/options/option-manager.js 229:12)
  -     at compile (~/Workspace/abc/node_modules/fly-esnext/node_modules/babel-core/lib/api/register/node.js 117:22)
  -     at normalLoader (~/Workspace/abc/node_modules/fly-esnext/node_modules/babel-core/lib/api/register/node.js 199:14)
  -     at Object.require.extensions.(anonymous function) [as .js] (~/Workspace/abc/node_modules/fly-esnext/node_modules/babel-core/lib/api/register/node.js 216:7)
  -     at Module.load (module.js 458:32)
  -     at tryModuleLoad (module.js 417:12)
  -     at Function.Module._load (module.js 409:3)
message: Cannot read property 'error' of undefined

The following are my dependencies with their respective version:

$ npm list --depth=0
[email protected] ~/Workspace/abc
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]

Rewrite `import` statements

At the very least, raw imports can be done easily:

import foo from 'bar';
//=> var foo = require('bar');

Handling multiple and/or partial imports will be more problematic:

import { foo, bar } from 'baz';
//=> var foo = require('baz').foo;
//=> var bar = require('baz').bar;

Handling aliases is the next step:

import * as foo from 'bar';
//=> var foo = require('bar');

import { foo as bar } from 'baz';
//=> var bar = require('baz').bar;

Concerns

Handling default exports (╯°□°）╯

References

#4, wendux/fly#239, wendux/fly#159 (comment)

Doesn't get applied to nested required files.

We usually set up our projects like below and then just require the sub tasks by using fs.readdirSync and looping over the files. This package is only accounting for the flyfile.js file.

tasks
├── build.task.js
├── clean.task.js
├── fonts.task.js
├── images.task.js
├── js.task.js
├── modernizr.task.js
├── server.task.js
├── styles.task.js
├── templates.task.js
└── watch.task.js
flyfile.js

I tried using babel-register and it will run the task but then fail fails with with this output.

[12:59:02] build failed because Cannot read property 'apply' of undefined
[12:59:02] Task chain was aborted!

packages

"babel-preset-latest": "~6.22.0",
"babel-preset-stage-0": "~6.22.0",
"babel-register": "~6.22.0",
"fly-esnext": "~2.0.0",
"fly": "~2.0.10-beta",