Skip to content
This repository has been archived by the owner. It is now read-only.

npmjs.org tells me that left-pad is not available (404 page) #4

Closed
silkentrance opened this issue Mar 22, 2016 · 193 comments
Closed

npmjs.org tells me that left-pad is not available (404 page) #4

silkentrance opened this issue Mar 22, 2016 · 193 comments

Comments

@silkentrance
Copy link

@silkentrance silkentrance commented Mar 22, 2016

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.

@tonytamps
Copy link

@tonytamps tonytamps commented Mar 22, 2016

according to https://registry.npmjs.org/left-pad

unpublished: {
  name: "azer",
  time: "2016-03-22T21:27:15.696Z",
  ...
}

It's causing Babel to fail installation

@silkentrance silkentrance changed the title npmjs.org tells me that left-pad is not available npmjs.org tells me that left-pad is not available (404 page) Mar 22, 2016
@silkentrance
Copy link
Author

@silkentrance silkentrance commented Mar 22, 2016

@tonytamps thanks for pointing this out

@azer why? this will break babel based builds on travis...

@Baggz
Copy link

@Baggz Baggz commented Mar 22, 2016

I'm having the same issue.

@jagthedrummer
Copy link

@jagthedrummer jagthedrummer commented Mar 22, 2016

Yep, I'm having the same problem.

@Baggz
Copy link

@Baggz Baggz commented Mar 22, 2016

Seems like https://www.npmjs.com/package/left-pad is up again, but no versions published.

image

@OllieJennings
Copy link

@OllieJennings OllieJennings commented Mar 22, 2016

@tonytamps it seems like the registry has updated weirdly

{
  "_id": "left-pad",
  "_rev": "12-29db2b53680e1c66ee1acc89502fe1b0",
  "name": "left-pad",
  "time": {
    "modified": "2016-03-22T21:42:18.002Z",
    "created": "2014-03-14T09:09:20.762Z",
    "0.0.0": "2014-03-14T09:09:20.762Z",
    "0.0.1": "2014-08-14T03:31:03.146Z",
    "0.0.2": "2014-08-15T07:13:09.056Z",
    "0.0.3": "2014-08-15T07:14:44.360Z",
    "0.0.4": "2015-05-20T04:04:04.473Z",
    "1.0.0": "2016-03-22T21:42:18.002Z",
    "unpublished": {
      "name": "westlac",
      "time": "2016-03-22T21:47:25.250Z",
      "tags": {
        "latest": "1.0.0"
     },

@camwest
Copy link
Contributor

@camwest camwest commented 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
Copy link

@jagthedrummer jagthedrummer commented 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
Copy link
Contributor

@camwest camwest commented Mar 22, 2016

@azer would know better why it was unpublished (assuming he was the one to unpublish it)

@jmcriffey
Copy link

@jmcriffey jmcriffey commented Mar 22, 2016

@camwest The package line-numbers is pinned to 0.0.3 specifically, so you'll need to publish that version or someone will have to summon the creator of line-numbers.

@silkentrance
Copy link
Author

@silkentrance silkentrance commented 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

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  v3.8.2
npm ERR! No compatible version found: left-pad@0.0.3
npm ERR! Valid install targets:
npm ERR! 0.0.9
npm ERR! 
npm ERR! 
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>
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

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...

@RongxinZhang
Copy link

@RongxinZhang RongxinZhang commented Mar 22, 2016

+1 same issue here.

@OllieJennings
Copy link

@OllieJennings OllieJennings commented Mar 22, 2016

@RongxinZhang try and use the new GitHub reactions instead of the old +1 :)

@olih
Copy link

@olih olih commented Mar 22, 2016

+1 same issue

@camwest
Copy link
Contributor

@camwest camwest commented Mar 22, 2016

@jmcriffey I can't publish 0.0.3 because it's already been published and removed. NPM forbids publishing a version of the same library twice.

See npm/npm-registry-couchapp#148 for context

@silkentrance
Copy link
Author

@silkentrance silkentrance commented Mar 22, 2016

@lydell is there a way to make line-numbers work again, perhaps an alternate package or by depending on left-pad@1.0.0 instead?

@danteoh
Copy link

@danteoh danteoh commented Mar 22, 2016

+1... this is messing things up for a lot of ppl.

@camwest
Copy link
Contributor

@camwest camwest commented Mar 22, 2016

See lydell/line-numbers#3

This pull request needs to be merged and line-numbers needs to be republished

@tomcat90
Copy link

@tomcat90 tomcat90 commented Mar 22, 2016

+1 Also broke my stuff

@phamcharles
Copy link

@phamcharles phamcharles commented Mar 22, 2016

Same

@anauleau
Copy link

@anauleau anauleau commented Mar 22, 2016

Same - broke my build

@laurelnaiad
Copy link

@laurelnaiad laurelnaiad commented Mar 22, 2016

This kind of just broke the internet.

@vhmth
Copy link

@vhmth vhmth commented Mar 22, 2016

It broked our build. Halp pl0x. Demo video for investors needs deploy soon. :-)

@laurelnaiad
Copy link

@laurelnaiad laurelnaiad commented Mar 22, 2016

My build wants version 0.0.3 back or else it's going to hold me hostage. npm reports the only valid install target is 0.0.9

@yentsun
Copy link

@yentsun yentsun commented Mar 22, 2016

was about to deploy after weeks of work (to demonstrate to the client) and bam - this issue.

@camwest
Copy link
Contributor

@camwest camwest commented Mar 22, 2016

@jacksonrayhamilton
Copy link

@jacksonrayhamilton jacksonrayhamilton commented Mar 22, 2016

It looks like someone (not me) completely removed left-pad from the npm registry

Time to update your password / credentials?

@davidmason
Copy link

@davidmason davidmason commented Mar 23, 2016

Didn't really expect to spend the last hours of my day cleaning up after another's tantrum.

@aduth so you're happy to use someone's code that they shared with the world for free, and you feel that your investment of $0 entitles you to some standard of service?

@drewhamlett
Copy link

@drewhamlett drewhamlett commented Mar 23, 2016

@davidmason Oh here we go again. Thanks a bunch.

@deoxxa
Copy link

@deoxxa deoxxa commented Mar 23, 2016

If anyone is confused about @davidmason's comment, it was in reference to a now-deleted reply. Anyone who has email notifications turned on in this thread probably has a copy in their inbox.

@zombieJ
Copy link

@zombieJ zombieJ commented Mar 23, 2016

Open source should not be oppressed. Though it cost others time, you have the reason to do that.

@joeandaverde
Copy link

@joeandaverde joeandaverde commented Mar 23, 2016

@davidmason the suck it up, you didn't earn it, move on mentality contributes negatively to the validity and trustworthiness of the OSS community.

@deoxxa
Copy link

@deoxxa deoxxa commented Mar 23, 2016

@joeandaverde the "you made it, you have to support the way I use it" mentality contributes negatively to the experience of being a part of the OSS community.

@matthew-dean
Copy link

@matthew-dean matthew-dean commented Mar 23, 2016

Safe harbor just means that NPM is safe (somewhat) from prosecution even if someone hosts copyrighted works on NPM. It doesn't mean they don't have to act on behalf of trademark / copyright owners.

@jackwanders
Copy link

@jackwanders jackwanders commented Mar 23, 2016

@jacksonrayhamilton thanks for the script; I made a tweak to output the full install path for any of @azer's packages found in a project:

#!/usr/bin/env bash
curl https://gist.githubusercontent.com/azer/db27417ee84b5f34a6ea/raw/50ab7ef26dbde2d4ea52318a3590af78b2a21162/gistfile1.txt \
    | sed 's/^\(.*\)$/\/\1$/' \
    > ~/suspicious-packages.txt \
    && npm ls --parseable \
    | grep -f ~/suspicious-packages.txt

This gave me the output:

/Users/jackwanders/some-project/node_modules/babel/node_modules/babel-core/node_modules/line-numbers/node_modules/left-pad

Hopefully this might help others determine how to proceed if they are relying on any of these packages.

@sphvn
Copy link

@sphvn sphvn commented Mar 23, 2016

Surely Kik could have just spent 5 seconds to realise that the NPM package had nothing to do with anything related to them. Solid effort on notifying a bunch of people as to what happened though.

Like others have said, his code can do what he wants with it, it's open source if you wish to republish then do so, rather than complain.

@iroy2000
Copy link

@iroy2000 iroy2000 commented Mar 23, 2016

Our build job caught that left-pad issues fortunately and we ended up upgrading one of our npm modules to its latest version which solve the problem, and my co-worker just swear in the team chatroom :)

@thesoftwarejedi
Copy link

@thesoftwarejedi thesoftwarejedi commented 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
Copy link
Member

@stevemao stevemao commented Mar 23, 2016

@azer transfer the module to me please 😄 since I'm the only other author of the module 😀

@azer
Copy link
Collaborator

@azer azer commented Mar 23, 2016

@stevemao is the new owner of the module, not sure how he can take the npm ownership.

@stevemao
Copy link
Member

@stevemao stevemao commented Mar 23, 2016

Thanks @azer 👍

@xzer
Copy link

@xzer xzer commented 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
Copy link

@isaacs isaacs commented Mar 23, 2016

@KoryNunn @SomeoneWeird @zerkms @drewhamlett If you run npm as root, it'll process.setuid() to a nobody user. https://docs.npmjs.com/misc/scripts#user

@KoryNunn
Copy link

@KoryNunn KoryNunn commented 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.

@winterbe
Copy link

@winterbe winterbe commented 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
Copy link
Collaborator

@azer azer commented Mar 23, 2016

@f teşekkür ederim anlayışın ve desteğin için Fatih :)

@tjacobs
Copy link

@tjacobs tjacobs commented 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?

@azer azer closed this Mar 23, 2016
@left-pad left-pad locked and limited conversation to collaborators Mar 23, 2016
@stevemao
Copy link
Member

@stevemao stevemao commented May 1, 2016

1.1.0 is released :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet