-
Notifications
You must be signed in to change notification settings - Fork 10
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
Build out passive compiler service using npm hooks #24
Comments
do we have a list of cross compilation targets?
I have an ancient build server that should be workable |
would probably need to figure out $$ if this is more than minor amounts of modules |
We have hosting and storage available. On Thu, Jun 2, 2016, 9:53 AM Bradley Meck notifications@github.com wrote:
|
if we want to use hooks instead of the changes feed i kind of see the user story like this... 🌵 creates a webhook with on change 💻 gets the 📦 events. if its a new publish or has never been seen we compile all of the versions otherwise just the new version. 💰 |
@soldair maybe I don't know enough about hooks, but can they compile onto existing/about_to_publish versions? |
nothing that cool yet. tessel has a build server i think and will host the binaries on s3. when folks push their code to the tessel, tessel will send the compiled versions to the device |
this pattern might be good for xcompiling more kinds of native modules though @bmeck. its more of an opt in rather than compile everything. im not sure whats better. |
@soldair taking that convo offline, little out of scope here |
The changefeed still works well for our purposes On Thu, Jun 2, 2016, 10:10 AM Ryan Day notifications@github.com wrote:
|
http://blog.npmjs.org/post/145260155635/introducing-hooks-get-notifications-of-npm
Here's what needs to be created:
The text was updated successfully, but these errors were encountered: