3 ms·

Not at all, I think they just have some notion that npm = bad and npm = (small) deps, so (small) deps = bad. I agree, it's harder to get right that it seems fr

Not at all, I think they just have some notion that npm = bad and npm = (small) deps, so (small) deps = bad. I agree, it's harder to get right that it seems from first glance. The number of implementations I've seen with broken or not-honoured timeouts... Python also had a retrying library; apparently it's no longer maintained. I've used the tenacity "fork", which has also evolved/introduced some great features like combinable and chainable wait/backoff.

oefrha 7y ago
> Not at all, I think they just have some notion that npm = bad and npm = (small) deps, so (small) deps = bad. No, I don’t have that notion. Apparently not every package on npm is small or trivial, but the abuse of trivial packages is most well-known and disastrous in the npm ecosystem. Edit: My god, iOS autowrong is all the rage today.