Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NPM: 429 Too Many Requests

github.com

Post reply on HN
Print view View original

51–60 of 171 posts

Re: NPM: 429 Too Many Requests

#51

Post by LandR »

dajonker wrote: post #43
gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

From the outside, it seems like Javascript developers are all in high school, participating in a popularity contest, feel the need to sprinkle emoji everywhere and communicate solely with memes and gifs.

>> participating in a popularity contest

This almost entirely explains the entirety of the javascript ecosystem and the seemingly ever increasing number of, and frequently changing popularity of, the various frontends frameworks. It seems a hype driven ecosystem, so it's not surprising it's also full of people posting memes and such.

Re: NPM: 429 Too Many Requests

#52

Post by ratata »

sethammons wrote: post #24

This is one of the reasons why, in Go, my team vendors our dependencies. For any service that seeks stability and the ability to deploy any time, removing networked build dependencies is important.

> vendors our dependencies

Is that like a local cache?

Re: NPM: 429 Too Many Requests

#53

Post by seemslegit »

dajonker wrote: post #43
gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

From the outside, it seems like Javascript developers are all in high school, participating in a popularity contest, feel the need to sprinkle emoji everywhere and communicate solely with memes and gifs.

well...

Re: NPM: 429 Too Many Requests

#54

Post by yellow_lead »

warpech wrote: post #9

If this happens in future, you can switch an NPM mirror, such as: - https://open-registry.dev/#get-started - https://npm.taobao.org/ WARNING: Research who runs the mirror before putting your trust in it. How to turn on: npm config set registry https://npm.open-registry.dev How to turn off: npm config delete registry

I would not recommend to use the Taobao registry though. This is operated by a Chinese company. Aside from the cybersecurity concerns, if it's hosted in China you'll be getting bad latency.

Re: NPM: 429 Too Many Requests

#55

Post by mFixman »

gmemstr wrote: post #6

This seems to be slowly clearing up. Regardless, can we talk about the conduct in this GitHub thread? I know every community is different but is it common to have memes and jokes posted this quickly and often in a GitHub issue? It makes it really hard to follow and discourages genuinely useful discussion of workarounds or progress.

Is this a new thing though? Bug threads about important issues were full of animated GIFs for the decade I've been following them.

Re: NPM: 429 Too Many Requests

#56

Post by kuon »

Isn't mirroring still a thing? I am not saying this as the old creepy guy (well a bit), but seriously wondering why a registry like npm doesn't have tons of geographicaly spreaded mirrors. Package can easily be signed and mirrored, that shouldn't be complicated.

Re: NPM: 429 Too Many Requests

#58

Post by alexandernst »

warpech wrote: post #9

If this happens in future, you can switch an NPM mirror, such as: - https://open-registry.dev/#get-started - https://npm.taobao.org/ WARNING: Research who runs the mirror before putting your trust in it. How to turn on: npm config set registry https://npm.open-registry.dev How to turn off: npm config delete registry

It really must be the end of the world for me to trust and switch to a Chinese NPM mirror.

Re: NPM: 429 Too Many Requests

#59

Post by blackandblue »

Hamuko wrote: post #46
MattRix wrote: post #36

Earlier quoted context omitted.

This is the first time I've seen "&c" used instead of "etc", I had to look it up. Interesting abbreviation!

Why would anyone use "&c" considering that it doesn't actually save any key presses?

i would! for the succinctness of it.

Re: NPM: 429 Too Many Requests

#60

Post by wojciechpolak »

imtringued wrote: post #18

Honestly, don't depend on central repositories for daily availability. Especially if you are doing CI that redownloads everything from scratch. Use something like artifactory to cache the repository you are using: https://www.jfrog.com/confluence/display/RTF/npm+Registry

Yup, artifactory helps a lot. The company where I work is using it and we run a lot of npm ci on a daily basis.
Post reply on HN