While every package doesn't register itself as Jam.js package, I appreciate the ability to install directly from GitHub. However, a gh:<user>/<repo>[/<branch>] url in the dependencies list in the package.json file fails.
This inconsistency is very annoying and makes distributing code without including external depencies impossible. (Which is a feature that dependency managers should provide [and why I love them!]) It makes me question the whole idea of including Jam.js in the project at all, as all it really provides in this case is a partially pre-configured require.js installation. (Mind you, I am a fan of jam.js. Most of the time, it just works.)
Contents of package.json:
Output of jam install
$ jam install
Building version tree...
repositories checking "gh:kriskowal/q"
Error: No package for 'gh:kriskowal/q'
at Object.exports.dependencyError (/usr/local/lib/node_modules/jamjs/lib/tree.js:227:16)
at Object.exports.updateDep (/usr/local/lib/node_modules/jamjs/lib/tree.js:192:33)
at Object.exports.addDependency (/usr/local/lib/node_modules/jamjs/lib/tree.js:139:28)
at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/jamjs/lib/couchdb.js:248:25)
A command line install of the same repo ($ jam install gh:kriskowal/q) works as expected, so I will not include its' output.
$ jam install gh:kriskowal/q
It will be great to have that!
Support of git repositories is a great idea, but it would be really nice to support more sources than just the registry or github.
Woa, dang it. Is there a specfic reason why github is the only supported service? And will this change? We use only bitbucket and a self hosted git service. This is quite a drawback indeed.
Closing, as it seems this project has died.