New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use node-pre-gyp for binary distribution. #89
Comments
That's probably a good idea. I guess the number of binaries is going to get quite large if I want to publish 0.10, 0.12 (is anyone using 0.11?) and io.js AND with/without native audio. I hope that's possible with node-pre-gyp. |
Distinguishing between io.js/node was added recently, so it should be ok but I'm not sure about audio - this might be more tricky. I guess it might be adressed by custom patterns. It's all in versioning section And I believe 0.11 is dead :) |
Do you know a good example that uses different node versions and architectures? To be honest I don't understand the documentation and what I am supposed to do. When the publish command is executed do I need all compiled binaries I want to distribute? Or can I publish one version (like 0.8) for different archs (like x86_64, arm) and node versions one after another? |
The documentation is indeed a bit confusing - when I was preparing configuration of my project I had to ask project owner some questions :) A good example is node-sqlite. If you want to I can prepare a sample config for node-spotify on my issue-81 branch :) Some more examples can be found on projects wiki |
Thanks, I'll take a look at node-sqlite. A kickstarter-sample config would be awesome! |
As of 0.7.3 node-spotify uses node-pre-gyp. I pushed a NodeJS 6 build to S3 (for Linux). Later I maybe will push builds for OSX and different NodeJS versions. node-pre-gyp builds will always use ALSA/OpenAL, if you don't want that you have to build from source. |
Distributing pre-built binaries with npm is impossible but there exists module called node-pre-gyp which (after small configuration) allows storing binaries in external location e.g. S3.
The text was updated successfully, but these errors were encountered: