Skip to content
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.

Aquifer doesn't work in 4.* LTS #184

Open
generalredneck opened this issue Jan 4, 2017 · 0 comments
Open

Aquifer doesn't work in 4.* LTS #184

generalredneck opened this issue Jan 4, 2017 · 0 comments

Comments

@generalredneck
Copy link
Contributor

In my testing, the latest version of aquifer doesn't work in the 4.* LTS version of Node. Though there is already a new LTS version 6., 4. will still be around as Active LTS until April, and then maintenance fixes afterward.

LTS Schedule

Since this is the case, we need to either fix the error:

/Users/allan/workspace/aquifer/lib/npm.api.js:77
      let npmModule = require(this.path)(...args) || false;
                                         ^^^

SyntaxError: Unexpected token ...
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:373:25)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/Users/allan/workspace/aquifer/bin/aquifer.js:23:13)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)

That happens even when you do an aquifer --version

Or we need to explicitly remove support for 4.* in package.json.

thebruce pushed a commit that referenced this issue May 14, 2017
…al flags. This should function similarly but work with v4. Fixes #184.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant