You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to size limits on npmjs.com, we had to disable some x86 for Android and x86_64 for iOS with 54ca156 and 58b948f. Ideally we'd be able to distribute the binaries for these platforms as well.
I couldn't find it documented but the size limit might be around 200mb packed. Without these architectures, the package is around 175mb.
Possible solutions I've thought of so far:
Don't include any binaries at all and let consumers build them on their own
Host the binaries somewhere else and download them with a package.json script on install
CC @olliiiver since you've contributed some fixes for the x86 builds in the past and might possibly be relying on them.
The text was updated successfully, but these errors were encountered:
I think removing x86 for Android is fine since most people are on x86_64 nowadays. I'm not entirely sure about Intel Macs after removing x86_64 for iOS, but looks like the Github workflows are still running.
We could think about having the prebuilds downloaded like node-canvas is doing it:
Oh, interesting. So we could attach the binaries to a GitHub release and then fetch them from there, e.g. with a postinstall step. That sounds feasible.
Due to size limits on npmjs.com, we had to disable some x86 for Android and x86_64 for iOS with 54ca156 and 58b948f. Ideally we'd be able to distribute the binaries for these platforms as well.
I couldn't find it documented but the size limit might be around 200mb packed. Without these architectures, the package is around 175mb.
Possible solutions I've thought of so far:
package.json
script on installCC @olliiiver since you've contributed some fixes for the x86 builds in the past and might possibly be relying on them.
The text was updated successfully, but these errors were encountered: