Packages removed due to compromise should not result in 404

When NPM 6.5.0 attempts to install a package that has been removed because it was compromised or depended on something that was compromised, the error should be less benign than a 404.

Currently it reports a 404 and then exits.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.