Try visiting this link:
/standalone/concat-stream@latest
Well, in this case, since someone has visited this link before you, the file was cached with leveldb. But if you were to try and grab a bundle that nobody else has tried to grab before, what would happen is this:
- The module gets pulled down from npm and installed
- The module gets browserified as a standalone bundle
- The module gets sent to you, piping hot
- The module gets cached so that you don't have to wait later on
There are a few API endpoints:
Get the latest version of :module.
Get a version of :module which satisfies the given :version
semver range. Defaults to latest.
The same as the prior two, except with --debug passed to browserify.
In this case, --standalone is passed to browserify.
Both --debug and --standalone are passed to browserify!
POST a body that looks something like this:
{
"options": {
"debug": true
},
"dependencies": {
"concat-stream": "0.1.x",
"hyperstream": "0.2.x"
}
}"options" is where you get to set "debug" and "standalone". Usually, in this
case, you'll probably only really care about debug. If you don't define
"options", this will default to { "debug": false, "standalone": false }.
"dependencies" is an npm-style deps hash.
What you get in return looks something like this:
HTTP/1.1 302 Moved Temporarily
X-Powered-By: Express
Location: /multi/48GOmL0XvnRZn32bkpz75A==
content-type: application/json
Date: Sat, 22 Jun 2013 22:36:32 GMT
Connection: keep-alive
Transfer-Encoding: chunked
{
"concat-stream": /* the concat-stream bundle */,
"hyperstream": /* the hyperstream bundle */
}
The bundle gets permanently cached at /multi/48GOmL0XvnRZn32bkpz75A== for
future GETs, but if you want to you can ignore that and just grab the included
body.
If you saved the 302 url from the POST earlier, you can just GET it instead of POSTing again.