I’ve been publishing early versions of rocket:module and Meteor gives me the familiar message:
You're not done publishing yet! This package contains binary code and must be built on all of Meteor's architectures, including
this machine's architecture.
You can access Meteor provided build machines, pre-configured to support older versions of MacOS and Linux, by running:
meteor admin get-machine os.osx.x86_64
meteor admin get-machine os.linux.x86_64
meteor admin get-machine os.linux.x86_32
meteor admin get-machine os.windows.x86_32
On each machine, run:
meteor publish-for-arch rocket:module@0.1.1
For more information on binary ABIs and consistent builds, see:
https://github.com/meteor/meteor/wiki/Build-Machines
but I don’t believe I have any NPM dependencies in rocket:module that are binary. I’ve moved the binary NPM libraries to rocket:webpack under the impression that only that package needs to be binary build for specific architecture when I update that package, so that way I don’t have to binary rocket:module every time I update some JavaScript.
Do I have the right impression about being able to separate the binary parts of a package into another package?