Install from private github url

[jamiebuilds]

Do you want to request a feature or report a bug? Bug

What is the current behavior?

You can't install a package like github:yarnpkg/yarn because it is private even though if

[2/4] 🚚  Fetching packages...
error git@github.com:yarnpkg/yarn.git: Tarball is not in network and can not be located in cache (/Users/thejameskyle/Projects/yarn-perf/git@github.com:yarnpkg/yarn.git)

What is the expected behavior?

It should be able to install the package like npm currently can.

[doot0]

This is also the case for private URLs that require basic authentication, e.g. git+https://gitusername:gitpassword@server/path/to/repo.git.

[milosivanovic]

I've provided a simple workaround for authenticating via SSH in yarn at #513 (comment) that you can use until this issue is fixed.

[martynchamberlin]

Looks like @ramasilveyra closed #971 in deference to #1081, but that PR didn't actually fix the problem, at least for me. I'm manually grabbing a non-published bleeding-edge version of yarn so that it will have #1081 in it, but I'm still getting this error:

Tarball is not in network and can not be located in cache [...]

Any suggestions what to change to get this to work?

[martynchamberlin]

Eh, ignore my comment. I had universally installed a stable release version of yarn and due to how my VM is setup, this was the one it was referencing instead of the bleeding-edge local version. So that's why I was getting that error. I've confirmed I no longer get that error on the latest version.

[balthazar]

Sorry for the close, I don't think this is resolved by my PR

[ramasilveyra]

#2992 added support for private git repos when using shorted repo syntax (this landed on v0.24.0).

The generation for the first time of a yarn.lock file works well, but then with a yarn.lock file if you try rm -rf node_modules && yarn fails with this error:

error An unexpected error occurred: "Invalid protocol: git+ssh:".

That error comes from https://github.com/request/request/blob/b12a6245d9acdb1e13c6486d427801e123fdafae/request.js#L455 and I think (im not sure, still looking to the code trying to understand) it's because yarn tries to use the tarball fetcher instead of the git fetcher.

Update

The offline feature/fix added recently makes the git resolver defaults to the tarball to avoid http calls https://github.com/yarnpkg/yarn/pull/3000/files
Returning the git shrunk if is possible seems to fix the issue look the last commit at https://github.com/ramasilveyra/yarn/tree/fix-private-deps

[bestander]

@ramasilveyra, do you have a PR in mind that could fix it?

[ramasilveyra]

@bestander Hey I just created a pr with the fix #3425, but I'm not sure if it's the best solution.

[chamini2]

This could be closed now, right?

[bilby91]

Last version fixes the problem.

[gsklee]

Just tried it and it doesn't work (github repo shorthand with private repo); it prompted me to enter my ssh key's passphrase but I cannot actually enter anything at all.

[gsklee]

Answering myself: #2992 (comment)

[onury]

This still doesn't work with yarn 1.3.2

Works —> npm i --save github:org/repo
Doesn't Work —> yarn add github:org/repo Got error: Permission denied (publickey)

macOS v10.13.1
Node v8.9.1
Yarn v1.3.2
npm v5.5.1

[jherdman]

This is definitely broken still, even with long form Git URLs.

[JoshuaCWebDeveloper]

I can confirm that the following do not work on Yarn 1.3.2 but do work on NPM:
yarn add github:org/repo
yarn add ssh://github.com/org/repo.git
yarn add ssh://git@github.com/org/repo.git
yarn add git+ssh://git@github.com/org/repo.git

However, using HTTPS does work on yarn:
yarn add https://github.com/org/repo.git

Unfortunately, in my case, there are dependencies that use some of the above formats, so it looks like I cannot use yarn until this issue is fixed.

[Schlammsuhler]

if you added you public key to your github account this works:
yarn add ssh://git@github.com:yarnpkg/yarn.git