Allow using a custom branch for the registry

[guybedford]

No description provided.

[mwq27]

Any movement on this issue?

[guybedford]

@mwq27 if you're able to share why this would be important to you, it would help to understand the need to prioritise it.

[mwq27]

There was a code fix in someone's PR that had not been merged in yet, but I wanted to install that specific branch to see if it worked in my own project. I thought it'd be nice if instead of doing jspm install npm:package I could point straight to that branch on github, like jspm install npm:[email protected]....., if that makes sense.

[guybedford]

@mwq27 this is actually a separate issue. jspm install github:owner/repo@branch is supported.

[mwq27]

Aaah ok cool, thank you

On Sat, Jan 2, 2016, 5:11 PM Guy Bedford [email protected] wrote:

@mwq27 https://github.com/mwq27 this is actually a separate issue. jspm
install github:owner/repo@branch is supported.

—
Reply to this email directly or view it on GitHub
#6 (comment)
.

[soulfresh]

I'm not sure if this is the use case you're looking for @guybedford but I'm using jspm-git to register a custom registry which points to a private stash repo.

> jspm install jspm-git
> jspm registry create stash jspm-git
ssh://[email protected]

When I try to install a branch from that stash repo, I get the error that there's no version match found. Something like:

> jspm install stash:user/repo@bugfix/branch-name
Looking up stash:user/repo

err  No version match found for stash:user/repo@bugfix%2Fbranch-name

warn Installation changes not saved.

I'm not sure if this is an issue with registry-endpoint or jspm-git.

[soulfresh]

Hmmm...I just tried installing a different branch with a name that didn't include the forward slash character and the install seemed to work. So it looks like the specific error I was seeing was actually related to folders in the branch name.

However, I noticed that installing different branches of a repo actually installs them side by side rather than replacing the existing repo. For example:

> jspm install stash:user/repo@master
> jspm install stash:user/repo@test-branch
> ls jspm_packages/stash/user/
repo@master    repo@test-branch

Is that the desired behavior? Is there a way to install stash:user/repo and then switch it to another branch? If I do something similar with npm, it replaces the existing install with the new branch version. jspm is not npm but the way npm does it seemed intuitive to me.

[guybedford]

@soulfresh yes / in branches is not supported well in jspm 0.16.

[Palid]

jspm install github:Palid/redux-form@fix/splice-is-undefined/#1082 - this command throws 404. Probably it doesn't recognise slashes and other special characters as intended.

[TomFoyster]

Has this been fixed yet??