3 ms·

Hmm, so there are 41K packages depending on 'request' but from now on everything that is merged into master is immediately going to be published? Sounds like a

• taspeotis 8y ago
  At least they're trying to manage it responsibly: > We’re going to have to remove inactive collaborators and enforce 2fa, because commit rights will effectively become npm publish rights.
• zamadatix 8y ago
  "Let’s just bump the major version when we deprecate. That way most people depending on the project won’t see this error until they try to upgrade to a new major, which means they are actively developing it and really should look for an alternative." You won't be able to enter the "recipe for disaster" without at least seeing the warning when you update your dependencies. At that point it's your prerogative if you want to continue with a deprecated package.