-
Notifications
You must be signed in to change notification settings - Fork 114
Npm package broken #28
Comments
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:
But the status is currently green. The fact that it installs fine some of the time (and if I do an Some pages online say you need to set the 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:
Once cleaned, the 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 For Leveller, it's defined as For hideShowPassword, it's defined as The NPM docs show examples that use the former (https), not the latter (git). I'm going to modify the |
Did not mean to close this. So, I implemented the package.json change, but then there's a new wrinkle... I found out that Still developing... |
@jeremylevy What a long, strange trip it's been! Thanks for bearing with us. Can you try |
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
Closing this issue now! |
The NPM package seems to be broken :
By the way, thanks for the good work. It works very well.
The text was updated successfully, but these errors were encountered: