Yearly reminder to vendor your dependencies.
NPM: 429 Too Many Requests
31–40 of 171 posts
Re: NPM: 429 Too Many Requests
#32I guess the solution here is for the larger CI providers to host a mirror of popular package repositories locally and provide an easy way to use them.
It really doesn't make a lot of sense to re-download tons of packages for every minor commit where you run your CI.
Re: NPM: 429 Too Many Requests
#33This 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.
It's disappointing. I commented saying as such - https://github.com/npm/cli/issues/836#issuecomment-586990343
> Posting memes/jokes in an issue wastes the time of people who actually need to be able to read through the issue.
> Stop it. Use emoji reacts if you feel the need.
In two minutes I have 24 dislikes and 13 likes. I think the introduction of emoji reactions was a bad idea, it gamifies the issues system.
Re: NPM: 429 Too Many Requests
#34This 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.
>It [...] discourages genuinely useful discussion of workarounds or progress.
Does it though? Sounds like an opinion.
Re: NPM: 429 Too Many Requests
#35Earlier quoted context omitted.
I think this is partly a result of two things. 1. GitHub presents an interface that encourages Reddit style behaviour. 2. NPM outages are essentially a meme in themselves at this point. Both of them together create a perfect storm.
I don't work with JS or related ecosystems, but how common are NPM outages?
It’s been super reliable, in my experience, and given their traffic volume, I’m pretty impressed with that.
Re: NPM: 429 Too Many Requests
#36This 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.
Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)
This is the first time I've seen "&c" used instead of "etc", I had to look it up. Interesting abbreviation!
Re: NPM: 429 Too Many Requests
#37Is it common to rely on a free service like npm for your company's core business? It seems like you would be taking a huge risk by not mirroring anything you need internally.
Re: NPM: 429 Too Many Requests
#38This 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.
The countless +1 and "Same here" comments without additonal info are a huge problem as well on Github. A simple click on a +1 button would suffice instead of a full comment. It's especially irritating when you follow a lot of issues hoping to get notified when there is a resolution but instead you get spammed by people making these pointless comments.
It makes it impossible to actually follow critical threads, as the notifications are completely worthless.
Re: NPM: 429 Too Many Requests
#39This 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.
Some people getting in the workforce in the last few years have troubles making the distinction between work and play contexts. It's extremely visible on github, slack, &c. which are more and more looking like discord / reddit (gifs, memes, random jokes in the middle of serious discussions)
Yep, noticed this on our local Teams groups too. The deluge of animations can be incredibly distracting and fill space making it more faf to go back and check details from earlier in the discussion.
Re: NPM: 429 Too Many Requests
#40This 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.
>It [...] discourages genuinely useful discussion of workarounds or progress. Does it though? Sounds like an opinion.
Sure, it's an opinion, but I've been keeping an eye on this issue since very early on, and I have seen some mentions of workarounds. Best of luck finding them, however, as they're buried somewhere in the middle.