Github user shazron commented on the issue:
https://github.com/apache/cordova-cli/pull/263
Final fix that worked: downgrade to npm@2
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featu
Github user shazron commented on the issue:
https://github.com/apache/cordova-cli/pull/263
@stevengill since `yarn` works flawlessly on `node 6` the alternative is,
put all the `install` commands in a script and use `yarn` when we detect `node
6`. Kinda like my script here:
https://g
Github user shazron commented on the issue:
https://github.com/apache/cordova-cli/pull/263
@stevengill unfortunately https://github.com/npm/npm/issues/9633 strikes
its head (see AppVeyor failure). Usually running `npm install` again fixes it,
but once the first `npm install` fails it
Github user stevengill commented on the issue:
https://github.com/apache/cordova-cli/pull/263
hows it going on this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and w
Github user shazron commented on the issue:
https://github.com/apache/cordova-cli/pull/263
Nah its https://github.com/npm/npm/issues/10343
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user shazron commented on the issue:
https://github.com/apache/cordova-cli/pull/263
Might be related: https://github.com/npm/npm/issues/9633
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user shazron commented on the issue:
https://github.com/apache/cordova-cli/pull/263
Now that I've got appveyor node versions "working", it reflects the node 6
failures on Travis. Now to get node 6 working (npm link shenanigans).
---
If your project is set up for it, you can re
