v0.33.0: allow installation of precompiled binaries with yarn@1

[ForsakenHarmony]

Feature request

What are you trying to achieve?

yarn add sharp with yarn v1.22.19

Is there any reason to not allow installation with yarn 1?

[lovell]

You may need to add the --ignore-engines flag for old versions of yarn.

Please see #3750 for the full context.

[mceachen]

@lovell Just upgraded to 0.33.0, but I'm also on yarn (v1). I guess I misread the instructions and tried to add a supportedArchitectures section to my package.json (which v1 doesn't use?)

I'd suggest adding to your installation verbiage that "yarn v1 requires --ignore-engines" and linking to this issue. That would have saved me some time.

[lovell]

yarn v1 has been in maintenance mode for almost 4 years. I understand people were (quite rightly) hesitant to upgrade yarn due to all the problems with "plug'n'play", but that feature can and should be switched off by setting nodeLinker to any value other than the default.

Using the --ignore-engines flag with v1 will probably work for many scenarios, but it will download every binary for every platform, which is a huge waste of time, energy, bandwidth etc. If you care about energy conservation then please upgrade to a modern package manager.

For those looking to use yarn for cross-platform installs via its supportedArchitectures feature, that was added in its v3.1.0 release.

[lovell]

I've updated the docs via commit 004fff9

If you're using yarn v1 please upgrade and set nodeLinker to anything other than pnp.