-
Notifications
You must be signed in to change notification settings - Fork 10
master: node 7.9 / yarn 0.23.2 build error node-gyp error: too few arguments to function call, expected at least 2, have 1 #140
Comments
I'm confused by the part where you did The situation may have changed, but last time I checked fibers wasn't compatible with node 7 yet, which means meteor users are stuck with node 6 until fibers (and possibly other libs) support node 7. |
Yup, we're stuck with node 6 right now: laverdet/node-fibers#333 (comment) |
Additionally, if someone is using the latest yarn version 0.23.2 (I don't know which other versions are affected - some time later than version 19), yarn uses node 7 and as far as I can tell can't be downgraded from brew. yarnpkg/yarn#1882 Other things I've tried...
|
Can you still install an old version with |
So I used |
Huh, why did you think it was weird? Generally package managers are designed to be relatively independent of language runtimes. Newer versions of node tend to be released with newer versions of npm, but you can actually install whatever version of npm you want, as far as I know... |
Marking that the resolution is added to the README.md, basically use nvm to manage multiple versions of node side-by-side; yarn uses whatever version of node the shell had loaded/linked |
== STR
$ brew install node
$ brew install yarn
$ git clone git@github.com:jcoreio/crater.git
$ cd crater
$ yarn
== FIXED WITH
$ brew uninstall node yarn
$ brew install --force node@6
$ brew link --force node@6
$ npm i
== Fresh install of OSX 2017-April-17
== ERROR log
The text was updated successfully, but these errors were encountered: