_From @tststs on February 12, 2015 9:45_
I used to get a dependency for a package i'm working on via
"tern": "git://github.com/marijnh/tern.git"
There seems to be no way since 0.177 to publish a package with this type of dependency.
The tern dependency range in the package.json file is invalid: git://github.com/marijnh/tern
Per design or issue?
thx
tststs
_Copied from original issue: atom/atom#5513_
Ahhh, I think I see what's causing problems for you -- as of recently, apm verifies that the semvers used in package.json are valid.
However, a dependency might be defined as a URL and a bunch of other things (I totally forgot about that):
https://docs.npmjs.com/files/package.json#dependencies
/cc @kevinsawicki
https://docs.npmjs.com/files/package.json#dependencies
I hope apm will support ALL types of valid dependencies at some point like npm?
I hope apm will support ALL types of valid dependencies at some point like npm?
I believe it should
I believe it should
But it doesn't. ref https://github.com/TypeStrong/atom-typescript/issues/163
URLs in the form of github:user/repo work. The github: protocol is required. See https://github.com/atom/apm/blob/v1.1.1/src/publish.coffee#L300