Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Rather than allow filters, it just spits out all the info it has locally and in the registry. If you want to filter the data, then that's what git is for.
|
|
|
|
|
|
|
|
|
|
It'd be REALLY nice if this bug got fixed:
https://issues.apache.org/jira/browse/COUCHDB-688
|
|
|
|
|
|
|
|
|
|
|
|
|
|
"scripts" hash.
|
|
fake require.paths entry.
|
|
|
|
|
|
While it's impressive to see a big list of files fly by, it's not very helpful for debugging, and is just noise.
|
|
it's running.
|
|
|
|
Use the registry and the cache to do crazy stuff, like publish a local tarball or folder. Also, package tarballs are added to the registry as couchdb attachments, so there's no reliance on github, and it's less likely that tarballs will go away or change after being published.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
JSON is always ascii, so use the faster encoding.
Share the string with callers, as well as the parsed data, for cases when I want to cache the json to a file locally.
|
|
action is required.
|
|
|
|
|
|
|
|
|
|
|
|
soon.
|
|
|
|
|
|
Grr... this one line fix made my npm demo a lot less worky.
|
|
|
|
|
|
|
|
|