Does the repository in package.json have to be an HTTPS path?


#1

I am trying to publish the language-emerald package which I am working on here.

I have some trouble using the HTTPS-based GitHub login due to my system set up (nixos), so I was wondering if I can’t make due with an SSH-based git login? I much prefer the SSH-based login anyway.

I tried just setting the repository to the SSH path, but this resulted in the following log:

Preparing and tagging a new version ✓
Pushing v0.1.0 tag ✓
Publishing language-emerald@v0.1.0 ✗
Creating new version failed: Git tag not found


#2

git@github.com:emerald/modes-atom.git

Are you sure that this is valid syntax? It‘s not listed in the npm documentation. Try github:emerald/modes-atom instead.

By the way, I‘m using https:// in all my packages and use SSH login for Git.


#4

By the way, I‘m using https:// in all my packages and use SSH login for Git.

But when you publish the package, don’t you still end up having to login via HTTPS for it to push the tag?


#6

Try github:emerald/modes-atom instead.

Then I get the following error:

ssh: Could not resolve hostname github: Name or service not known

#7

I have my credentials stored in my keychain (ssh-add -K)