search

browserify / wzrd.in

browserify as a service.
http://wzrd.in
MIT License
638 stars 96 forks source link

specify node/browserify version to use when bundling #146

Open max-mapper opened 8 years ago

max-mapper commented 8 years ago

We have to globally upgrade node and browserify right now which on the one hand is nice because we get new versions, but is bad from an API standpoint because the same GET request to wzrd.in one day might return different results the next day.

It would be cool if we strived towards reproducibility by default in the HTTP API, so you could specify the node + browserify versions in the GET requests to build a module in a specific environment

Maybe combined with https://github.com/jfhbrook/wzrd.in/issues/117 this wouldn't be too bad to implement

jfhbrook commented 8 years ago

I've been thinking about exposing a number of new APIs, either under separate routes or under a /v2/ namespace. This could be a good way to do this.

An open question here is what to do when we don't feel like supporting tomorrow's 0.10 anymore.

jfhbrook commented 8 years ago

As far as how docker can enable this: We can extend the docker stuff to adjust node version using nvm, frontloading the node install in the image for speed. There isn't a similar tool that I know of for npm, though I would very much like one to exist.