Can't download a private repo? about napa HOT 8 CLOSED

It appears that you cannot. Although I imagine if it is a private repo convincing the maintainer to add a package.json would be easy.

from napa.

It's exactly what I've done ;) Added a package.json :D

Maybe should be mentioned in the readme?

from napa.

I'm somewhat confused by this issue. napa is using git, so as long as you have network access to the repo you'd like to provide, you should be fine. To me this is more of a configuration error than an issue with napa.

from napa.

It does work with me as well. I access private repos over the git+ssh protocol. Haven't tried it with github private repos though.

from napa.

Doesn’t appear to work with GitHub private repos. Target repo has a package.json.

Tried the following:

• username/repo // silently fails (no errors but module does not appear in node_modules/)
• git+ssh://[email protected]/repo // silently fails
• git+ssh://github.com/username/repo.git // ERR! Permission denied (publickey).
• git+https://github.com/username/repo.git // Halts installation to prompt for authentication. Works, but I had to generate a new application-specific password for Napa.

Would be ideal if Napa could use my SSH public key, same as NPM does. For example, this works without any additional configuration or new application-specific passwords:

"dependencies": {
  "repo": "git+ssh://[email protected]:username/repo.git"
}

from napa.

Personally, I think this should be closed as wontfix.

As invaluable as napa is, at the end of the day it is a workaround for unmaintained and non-compliant packages, and I don't think we should be encouraging workarounds considering I can't fathom a situation you would not be able to add a package.json to a private repo.

from napa.

This is even more relevant w/ new npm private modules.

from napa.

Good point, thanks @caseyWebb!

from napa.