Every time this pops up, I'm reminded of the day that the NPM registry started returning 418 responses for users accessing it via corporate HTTP proxies. I rem

Every time this pops up, I'm reminded of the day that the NPM registry started returning 418 responses for users accessing it via corporate HTTP proxies. I remember being at a training course that day and my manager asking me what we could do to fix it because our CI was failing to pull dependencies from NPM. Trying to explain that NPM was returning a status code intended as an April Fools joke and which was never meant to see the light of production was quite difficult Perhaps I can fix a lot of things but debugging a response code that isn't meant to exist is not one of them. https://github.com/npm/npm/issues/20791 https://github.com/npm/npm/issues/20791