This repository was archived by the owner on May 9, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on May 9, 2019. It is now read-only.
npmjs.org tells me that left-pad is not available (404 page) #4
Description
When building projects on travis, or when searching for left-pad on npmjs.com, both will report that the package cannot be found.
Here is an excerpt from the travis build log
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v4.2.2/bin/node" "/home/travis/.nvm/versions/node/v4.2.2/bin/npm" "install"
npm ERR! node v4.2.2
npm ERR! npm v2.14.7
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/left-pad
npm ERR! 404
npm ERR! 404 'left-pad' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'line-numbers'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! Please include the following file with any support request:
npm ERR! /home/travis/build/coldrye-es/pingo/npm-debug.log
make: *** [deps] Error 1
And here is the standard npmjs.com error page https://www.npmjs.com/package/left-pad
However, if I remove left-pad from my local npm cache and then reinstall it using npm it will happily install left-pad@0.0.4.
Activity
tonytamps commentedon Mar 22, 2016
according to https://registry.npmjs.org/left-pad
It's causing Babel to fail installation
[-]npmjs.org tells me that left-pad is not available[/-][+]npmjs.org tells me that left-pad is not available (404 page)[/+]silkentrance commentedon Mar 22, 2016
@tonytamps thanks for pointing this out
@azer why? this will break babel based builds on travis...
Baggz commentedon Mar 22, 2016
I'm having the same issue.
jagthedrummer commentedon Mar 22, 2016
Yep, I'm having the same problem.
Baggz commentedon Mar 22, 2016
Seems like https://www.npmjs.com/package/left-pad is up again, but no versions published.
OllieJennings commentedon Mar 22, 2016
@tonytamps it seems like the registry has updated weirdly
camwest commentedon Mar 22, 2016
Yeah I published a 1.0.0 to try to resolve the dependency. It looks like someone (not me) completely removed left-pad from the npm registry
jagthedrummer commentedon Mar 22, 2016
Is there a way to get all the old versions back again? In my project it's at the end of a fairly long dependency chain...
camwest commentedon Mar 22, 2016
@azer would know better why it was unpublished (assuming he was the one to unpublish it)
jeffrifwald commentedon Mar 22, 2016
@camwest The package
line-numbersis pinned to0.0.3specifically, so you'll need to publish that version or someone will have to summon the creator ofline-numbers.silkentrance commentedon Mar 22, 2016
Just tried replacing the travis version of npm which is fairly old by a the latest and see what it will do
It will now tell me that there is a version 0.0.9... weird.
Will not try to install that one, though, with all the malware going around...
roughpandaz commentedon Mar 22, 2016
+1 same issue here.
OllieJennings commentedon Mar 22, 2016
@RongxinZhang try and use the new GitHub reactions instead of the old +1 :)
olih commentedon Mar 22, 2016
+1 same issue
167 remaining items
thesoftwarejedi commentedon Mar 23, 2016
This is a great example of why decentralizing the package hosting can solve the problem. If package hosting were done via a technology such as zeronet and torrents, this could be entirely avoided.
I'll be looking into this in the coming months.
stevemao commentedon Mar 23, 2016
@azer transfer the module to me please 😄 since I'm the only other author of the module 😀
stevemao commentedon Mar 23, 2016
https://github.com/azer/left-pad/graphs/contributors
azer commentedon Mar 23, 2016
@stevemao is the new owner of the module, not sure how he can take the npm ownership.
stevemao commentedon Mar 23, 2016
Thanks @azer 👍
xzer commentedon Mar 23, 2016
Thanks @azer, you did right thing which makes us understand how the npm is dangerous to us, open source developers. You did perfect warning to all the world to tell us do not trust the bullshit npm any more.
To be honest, great work!
isaacs commentedon Mar 23, 2016
@KoryNunn @SomeoneWeird @zerkms @drewhamlett If you run npm as root, it'll
process.setuid()to anobodyuser. https://docs.npmjs.com/misc/scripts#userKoryNunn commentedon Mar 23, 2016
@isaacs that is really good. There are however many other malicious things that can be done without sudo, like grabbing private keys.
f commentedon Mar 23, 2016
We're with you @azer!
https://medium.com/@azerbike/i-ve-just-liberated-my-modules-9045c06be67c#.eww19oprb
winterbe commentedon Mar 23, 2016
I don't wanna imagine what happens when tomorrow someone trademarks Lodash and wreaks havoc. 💥
Maybe it's time to add an exclusion clause to Open Source licenses for companies like Kik?
BTW: Ask one of 80 million germans about Kik and they'll recognize a completely different company.
azer commentedon Mar 23, 2016
@f teşekkür ederim anlayışın ve desteğin için Fatih :)
tjacobs commentedon Mar 23, 2016
This is why Docker exists. Because dependency management is trouble. Pack it all into one package. Do we need a Docker for JS?
stevemao commentedon May 1, 2016
1.1.0 is released :)