Allow yarn to be used instead of npm

[soredake]

Lines like this preventing normal use with yarn:
child.exec('npm prune --production', {cwd: appPath}, cb)
exec('npm install --no-bin-links'

[malept]

That's preventing yarn completely replacing npm, sure. In the meantime you should be able to symlink npm to yarn and in theory it should "just work".

[soredake]

yarn prune has no --production option
yarn install has no --no-bin-links option, so just symlink is not the solution (while sed -i /npm --option/yarn --option, but it is not so convenient)

[malept]

Then it sounds like yarn support specifically is blocked on prune --production being added. That is an important part of how we package Electron apps.

[soredake]

yarnpkg/yarn#696 (comment)

[malept]

The above yarn issue relates to prune. This one relates to --no-bin-links: yarnpkg/yarn#929

Those two issues block proper yarn support. However, I have spec'd out how to implement generic NPM-compatible package manager support in #515 (comment), and I am happy to review pull requests that implement this (and, obviously, follow the contributing guidelines).

[soredake]

yarnpkg/yarn#1651

[soredake]

yarnpkg/yarn#696 (comment)

[ghost]

--no-bin-links did finally happen, but still no resolution for the other issue.