Josh Holbrook
Josh Holbrook
@voronianski figure out how to get me your pubkey and I'll add it to the box and give you a tour No pressure, but the ability to do something when...
If Max +1's it, I'm cool with it.
Might be mutually exclusive with #107 .
The "right move" here is, once the docker stuff lands, name the docker container, create a timeout on build start, and kill the container if the timeout occurs. Some interesting...
https://github.com/docker/docker/issues/1905
One suggestion is to just use npm for that, since this would basically be proxying to npm anyway.
It occurs to me that npm might not be CORS-enabled like browserify-cdn is. That, and there's all kinds of other information this could support (such as cache information).
For all the node version errors: https://github.com/browserify/wzrd.in/blob/master/test/builder.js#L17 this is just a bad test, it was written when node 6 was LTS and it was fine for what I was doing...
sort of - I'm the original author.
I figured the link on wzrd.in to the standalone concat-stream was sufficient. What do you have in mind?