> Still, others point out that the npm blog announcing 5.7.0 certainly reads like an official release announcement. Ok, granted, this much is true. But so far

> Still, others point out that the npm blog announcing 5.7.0 certainly reads like an official release announcement. Ok, granted, this much is true. But so far as I know, you'd have to be using npm@next to have gotten 5.7.0, not just the regular npm package. I'll fully agree that npm should not have introduced a bug like this, but how great of an idea is it to run bleeding edge versions in production?