3 ms·
You bake deprecation notices into npm, to be displayed during install. He has more than 3m installs a month, if he really wanted to, he could have easily displa
by felixrieseberg 11y ago
You bake deprecation notices into npm, to be displayed during install. He has more than 3m installs a month, if he really wanted to, he could have easily display a giant "npm sucks" banner during every single install. Same message, but it wouldn't immediately hurt people who trusted his modules.
- wolfgke 11y ago> Same message, but it wouldn't immediately hurt people who trusted his modules. Perhaps he wanted (because of his rage on npm) to hurt people that trust(ed) npm?
- karmelapple 11y agoI'd be very curious to know if this was true, because the actions taken certainly seem like that's the possible intent.
- vacri 11y agoOur build system eats deprecation notices with eggs for its breakfast. While I'm sure that they exist, I've never worked with a developer who paid much attention to deprecation notices unless they were looking to actively update a module.
- akx 11y agoThey'd notice it when doing a local `npm i` for development.
- alpb 11y agoI highly doubt if most continuous build/delivery systems actually have a person looking at the build output to take some action. That’s why, centralized build systems should not just let the packages disappear but unfortunately that’s not the reality. This is also the reason why there are languages like Go out there that do not rely on centralized package management.