Hacker GitHub

← All repos

npm/registry

View on GitHub ↗ ★ 499

npm registry documentation

16 mentions on Hacker News by 16 people: 4 stories, 12 comments · first 2016-06-28 · latest 2023-07-25

Mentions per year 16 mentions · busiest year 2018 (11)
20082026
AllStoriesComments NewestTopOldest
  1. …takes security than a namespace that may change hands. NPM exposes that info in the _npmUser field: https://github.com/npm/registry/blob/master/docs/REGISTRY-AP... . That gives "name" (NPM username) and email. While there are thousands of…
    comment by koolba · 2023-07-25 · in Social engineering campaign targeting tech employees spreads through NPM malware
  2. ▲ 2
    NPM ERR 429 Too Many Requests
    story by bjornstar · 2018-05-31 · 0 comments
  3. They say they've fixed this in this related issue ( https://github.com/npm/registry/issues/335 ) but I can't tell what change was made. The only discussion was around accepting a port number in the Host header. All well and good to fix…
    comment by skywhopper · 2018-05-29 · in NPM proxy users receiving ERR 418 I'm a teapot
  4. …restored all the package-versions for the 9 packages that were published over" Full context here https://github.com/npm/registry/issues/255
    comment by kkapelon · 2018-03-30 · in Time for developers to address the chaos of Node.js and NPM
  5. …package names in package.json? [0] https://www.theregister.co.uk/2016/03/23/npm_left_pad_chaos [1] https://github.com/npm/registry/issues/255 *edit: formatting
    comment by officialchicken · 2018-02-22 · in Do not use NPM 5.7
  6. …breaking builds. But it looks like third parties were able to take over the missing packages, see https://github.com/npm/registry/issues/256 - which is a HUGE deal, considering "npm install" blindly executes the scripts in a package's…
    comment by 0x0 · 2018-01-06 · in Many packages suddenly disappeared
  7. Apparently the restore is now complete: https://github.com/npm/registry/issues/255#issuecomment-3557...
    comment by sublimino · 2018-01-06 · in Many packages suddenly disappeared
  8. There are over 700 comments on this issue on GitHub. It is turning into live chat room. https://github.com/npm/registry/issues/255 Be part of the history :) EDIT: there are now over 1100 comments/memes.
    comment by batina · 2018-01-06 · in Many packages suddenly disappeared
  9. …missing. EDIT: it's back [1]: https://stackoverflow.com/questions/48131550/nodemon-install... [2]: https://github.com/npm/registry/issues/255
    comment by ben_jones · 2018-01-06 · in Many packages suddenly disappeared
  10. …just disapperead, now some are re-appearing, potentially uploaded by differnt users (!). See https://github.com/npm/registry/issues/255 for details. Very annoying, breaks builds all over, also prevents installing react-native.
    comment by the_duke · 2018-01-06 · in Many packages suddenly disappeared
  11. ▲ 749
    Many packages suddenly disappeared
    story by xxkylexx · 2018-01-06 · 492 comments
  12. Also see: https://github.com/npm/registry/issues/255
    comment by JonathanBouman · 2018-01-06 · in NPM: Many packages and/or versions have disappeared
  13. ▲ 3
    Is the npm registry still open source?
    story by setra · 2017-12-19 · 0 comments
  14. I'd switch to scoped packages, if not for https://github.com/npm/registry/issues/59
    comment by pseudobry · 2017-03-23 · in Announcing Free Orgs at npm
  15. …Edit: Apparently there is a Github issue for this[1] [0]: https://www.npmjs.com/package/d [1]: https://github.com/npm/registry/issues/38
    comment by chrisfosterelli · 2017-01-16 · in The owner of several 1 letter NPM packages
  16. ▲ 1
    Programmatically access all the public npmjs registry data: a tutorial
    story by ag_dubs · 2016-06-28 · 0 comments