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

Getting error when running danger locally #636

Open
ashkan18 opened this issue Jul 17, 2018 · 1 comment
Open

Getting error when running danger locally #636

ashkan18 opened this issue Jul 17, 2018 · 1 comment

Comments

@ashkan18
Copy link

Problem

Danger is locally crashing for me with following setup:

Now using node v8.4.0 (npm v5.3.0)
Found '/Users/ashkinas/src/metaphysics/.nvmrc' with version <v8.4.0>
N/A version is not installed yet

> husky - npm run -s prepush
> husky - node v5.10.1

yarn run v1.1.0
$ "/Users/ashkinas/src/metaphysics/node_modules/.bin/danger" "local"
/Users/ashkinas/src/metaphysics/node_modules/parse-diff/index.js:120
    ref = current.changes, [recentChange] = slice.call(ref, -1);
                           ^^^^^^^^^^^^^^

ReferenceError: Invalid left-hand side in assignment
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:387:25)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at Object.<anonymous> (/Users/ashkinas/src/metaphysics/node_modules/danger/distribution/platforms/git/diffToGitJSONDSL.js:3:17)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

> husky - pre-push hook failed (add --no-verify to bypass)
> husky - to debug, use 'npm run prepush'
error: failed to push some refs to '[email protected]:ashkan18/metaphysics.git'
@orta
Copy link
Member

orta commented Sep 22, 2018

I wonder if that's running with an older build of node that doesn't support the const [a] = [1] style syntax ( where a would be 1 here)

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

2 participants