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 about crater

[jedwards1211]

I'm confused by the part where you did brew install --force node@6, what was that for?

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.

[jedwards1211]

Yup, we're stuck with node 6 right now: laverdet/node-fibers#333 (comment)

[Falieson]

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
I'm running into this issue after a fresh install of osx.

Other things I've tried...

~ ❯❯❯ brew install [email protected]
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (homebrew/core).
==> Updated Formulae
exiftool                   lcdf-typetools             unzip
kibana                     libtorrent-rasterbar

Error: No available formula with the name "[email protected]"
==> Searching for a previously deleted formula...
Error: No previously deleted formula found.
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
==> Searching taps...
Error: No formulae found in taps.

[jedwards1211]

Can you still install an old version with npm i -g?

[Falieson]

So I used nvm after your suggestion and submitted a PR for using .nvmrc with the package.
Also I just figured out that yarn (v0.23.2) will use whatever version of node the environment is using and it isn't strictly associated with node7 (I thought that was weird!)

[jedwards1211]

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...

[Falieson]

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