np
np copied to clipboard
Doesn't finish "Publishing package" step even though repo shows a successful publish.
This is a similar report from #167 but it occurs when publishing to npm
?
I get the email stating it was published successfully (which it does) but it never completes through np
which means the tag task never executes. Further, how does np
determine if yarn should be used over npm
I'm not using Yarn, so can't really help much with that. Yarn support is community-contributed. Maybe @gillchristian @jescalan @ianwalter @tusbar can help.
Further, how does np determine if yarn should be used over npm
It uses https://github.com/sindresorhus/has-yarn
I'm having the same issue but with npm.
The package has published successfully, but np hangs on the publishing step. When I ctrl-c out of it the version in my package.json gets rolled back and no update happens in git.
@resurge I think that the issue you're experiencing is #79 (which you could bypass using a hack - see https://github.com/sindresorhus/np/issues/79#issuecomment-249527282).
@resurge I think that the issue you're experiencing is #79 (which you could bypass using a hack - see #79 (comment)).
Hmm, possibly. However I tried the workaround without success. When tapping the enter key the line "Prerequisite check" gets duplicated.
My private key doesn't have a passphrase set. So I tried my npm password, assuming it's the npm password prompt that was waiting for a password there, but without success.
(I tapped enter a lot of times :p)
This was a new package/git repo just for the purpose of testing the workaround.
got the same problem using npm :)
any new update on this issue?
further info
actually the bug magically goes-away when version reaches
v0.0.11
Strange... I have been using this for about a month now and just experienced this for the first time. Typing in a password disappears and pressing enter duplicates the "Prerequisite check", like others have said.