Repository navigation
Npm package broken #28
Description
Activity
Hrm, I'm encountering the same error. Thanks for letting us know, we'll investigate...
Huh, it worked for me a moment ago, but for @erikjung it did not.
According to NPM's Troubleshooting page:
- It's most likely a temporary npm registry glitch. Check npm server status and try again later.
- If the error persists, perhaps the published package is corrupt. Contact the package owner and have them publish a new version of the package.
But the status is currently green. The fact that it installs fine some of the time (and if I do an
npm install ~/my/local/folder/hideShowPassword, that works fine, too) suggests that corruption is unlikely.Some pages online say you need to set the
npmregistry, but runningnpm config get registryfor me outputs the correct registry URL (https://registry.npmjs.org/).Most perplexing, one of our other npm modules doesn't seem to have this problem at all...
Still investigating....... 💭
It worked for me BEFORE my npm cache was cleaned with:
npm cache cleanOnce cleaned, the
npm installhas broken.Thanks for the support !
Yeah, that seems to be the case for me as well... cleaning the cache makes it break again.
@lyzadanger pointed out that it's perplexing to see zero downloads on the npm page, compared to another package which has many downloads despite being far less popular (it has about 1% of the amount of GitHub stars). Something's not right there!
I'm comparing the two
package.jsonfiles and noticing a discrepancy in the way therepository.urlfield is specified.For Leveller, it's defined as
https://github.com/cloudfour/leveller.git.For hideShowPassword, it's defined as
git://github.com/cloudfour/hideShowPassword.git.The NPM docs show examples that use the former (https), not the latter (git).
I'm going to modify the
package.jsonand push a new version to see if that remedies the issue or not.- added a commit that references this issue
on May 13, 2015 Did not mean to close this.
So, I implemented the package.json change, but then there's a new wrinkle... I found out that
npmdoesn't allow publishing of packages with capital letters in their names. I'm not sure how we got a registry page at all before, but apparently that was a fluke or an oversight or a hiccup or something.Still developing...
- added a commit that references this issue
on May 13, 2015 @jeremylevy What a long, strange trip it's been! Thanks for bearing with us.
Can you try
npm install hideshowpassword(all lower-case) and see if that resolves your issue?It works ! You rock ! 👍
@jeremylevy Great, thanks so much for reporting this issue! It's embarrassing to think how long this npm package may have been broken. 😓
I spoke with the folks at NPM and they recommended deprecating
hideShowPassword. So now, if you attempt to install the camel-case version, you should see a warning that advises you to use the lowercase version instead:$ npm install hideShowPassword npm WARN deprecated [email protected]: use lowercase version: hideshowpassword ...Closing this issue now!
The NPM package seems to be broken :
By the way, thanks for the good work. It works very well.