Consider using prebuildify over prebuild-install for version 3.x

[exige81]

Feature Request:

Replace prebuild-install with prebuildify

Motivation:

prebuildify ships prebuilt binaries inside the npm package in lieu of storing them on github.
prebuild-install itself currently recommends using prebuildify over prebuild-install

This provides a lower friction installation experience for the end user, especially for those behind a firewall or in enterprise environments where access to github is limited. prebuild-install can be configured with a host mirror, but this adds further complication and isnt always straightforward as evidenced by the several issues created surrounding the inability to reach the prebuilt binaries on github.

prebuildify also is compatible with N-API

[btsimonh]

could be interesting. But canvas has a LOT of binaries (74 Mbytes on windows - although actually only 27mbytes are required - seems the binary dist contains the pdb and obj files!).
But, if we had the four primary platforms, windows, macos x 2, linux, we could expect the overall binary loading to be ~100mbytes or more, when each install will only use ~25 Mbytes of this.

[legap]

I just stumbled over this issue prebuild/prebuild-install#216 in the prebuild-install project.
They plan to deprecate prebuild and then prebuild-install in favor of prebuildify & node-gyp-build.
And as canvas is the leader of the most downloaded packages with dependencies to it, this issue will get important.

[chearon]

Prebuildify bundles all architectures in 1 package I think? Our binaries are too big for that, but I am planning on using optionalDependencies along with os, cpu, and libc for v4, which should achieve the same goal (and it's well supported).

I hope to get v4 released midyear. Progress can be tracked in #2476.

[chearon]

optionalDependencies is implemented in v4 (#2602)!

npm install canvas@next