9 ms·
I tend to get bizarre and seemingly incorrect network errors randomly from various npm packages from time to time. Yarn does it too (sometimes worse). They will
by sli 7y ago
I tend to get bizarre and seemingly incorrect network errors randomly from various npm packages from time to time. Yarn does it too (sometimes worse). They will fail with a network error yet I can reach both the package repository and the package files themselves just fine using a browser, and the problem will persist for a while. It might be that.
- everybodyknows 7y agoThat's indeed the case with my failures, persisting for two days now. I suspected filtering based on something in HTTP headers, but spoofing the User-Agent string with one copy-pasted from Firefox yielded no change. Command-line NPM has an option for the User-Agent spoof -- but not much otherwise, and I guess there's plenty of other metadata for T-mo to fingerprint on.