semver support for github repos #4527

Closed
tj opened this Issue Jan 22, 2014 · 6 comments

Comments

Projects
None yet
3 participants
Contributor

tj commented Jan 22, 2014

I can send a patch if it would be accepted. It's also quite a bit faster than using git clones which is nice.

Member

domenic commented Jan 22, 2014

Dupe of #3014, #3328, #3347, #3442, and #3511. @isaacs doesn't want this feature, unfortunately.

@domenic domenic closed this Jan 22, 2014

Contributor

tj commented Jan 22, 2014

is there any real reason? or is it just to force us to use paid stuff? if not that's fine, I'm alright with maintaining the fork, but I have a feeling a lot of people are going to start migrating to it, and the implementation is small and simple so I don't see why not really

Contributor

tj commented Jan 22, 2014

vendor lock-in is great too 👍 especially when it's super broken and we can't get any work done at all

Contributor

guybrush commented Jan 22, 2014

hey @visionmedia i wonder how that patch looks like, i thought about this some time and could not think of a solution

anyway you can already use "semver-branches", which kinda sucks because you have to manage all the branches by hand. and there would be quite a lot after some versions, depending on what ranges you want to support :p although a tool could be written to do it for you

Contributor

tj commented Jan 22, 2014

it's really simple but getting it to cooperate with npm caching internals seems to be a different story :(

Contributor

tj commented Jan 22, 2014

I'll publish it to my fork of npm once I have that figured out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment