[RRFC] Deprecated packages: automatically display dependents, to ease notifying maintainers #155

Activity

1. isaacs commented on May 29, 2020

   

   isaacs

   on May 29, 2020

   Contributor

   More actions

   This is a good idea, but I wonder if it even needs an RFC. I'd be fine just doing this in npm v7. The only downside I could imagine is that it might get a bit noisy if you have a popular module that's deprecated, or a bunch of deprecated modules under a single top level dep.

   There's definitely a need for us to rethink a lot of the design of our various warning outputs, this would be a good candidate for consideration there.
2. dandv commented on May 30, 2020

   

   dandv

   on May 30, 2020

   ContributorAuthor

   More actions

   I'd be happy to see that in v7 as well. Should I file the issue somewhere else (it can also be moved to a different GitHub repo by an org owner, but no problem to file it again in the cli repo for instance).

   As for popular deprecations, the noise should incentivize solutions :)
3. ruyadorno commented on Sep 23, 2020

   

   ruyadorno

   on Sep 23, 2020

   Contributor

   More actions

   I think this idea goes really well with the new npm explain command! Let me put it in the agenda so that we can get it back in our radar for post-v7.0.0.
4. ruyadorno

   added

   Agendawill be discussed at the Open RFC callwill be discussed at the Open RFC call

   on Sep 23, 2020
5. ruyadorno commented on Oct 21, 2020

   

   ruyadorno

   on Oct 21, 2020

   Last edited by ruyadorno

   Contributor

   More actions

   Action item from the OpenRFC call:

   • Follow up RFC/PR that adds a post-install notification (similar to audit and fund) that aggregates the number of deprecated packages and surfaces that info to the user while also removes all the current warnings during install time, user then could optionally run a subcommand such as npm explain deprecation in order to get the detailed info.
6. ruyadorno commented on Oct 21, 2020

   

   ruyadorno

   on Oct 21, 2020

   Last edited by ruyadorno

   Contributor

   More actions

   Thanks for bringing up this idea @dandv! Feel free to follow up with the proper RFC if you're interested in championing this change 😊 otherwise it will just have to wait a little longer until someone from the team has the bandwith to pick it up but after the discussion in the call it def sounds like an area we want to improve in the cli. Thanks again for your contribution 😄
7. darcyclarke commented on Oct 21, 2020

   

   darcyclarke

   on Oct 21, 2020

   Last edited by darcyclarke

   Contributor

   More actions

   @dandv @ruyadorno Just to quickly follow up, I think npm explain deprecation should actually be npm explain --deprecation (since explain currently expects the second arg to be a spec). Thinking about it a bit as well, it may make sense that the same flag is supported by npm ls 🤔. Either way, an example of how this could work/look:

   $ npm install express@2

   added 6 packages, and audited 6 packages in 870ms
   
   3 deprecated packages found
   
   To find out more, run:
     npm explain --deprecated 
   
   4 vulnerabilities found (1 low, 1 moderate, 2 high)
   
   To address all issues (including breaking changes), run:
     npm audit fix --force
   
   Run `npm audit` for details

   👍React with 👍2Reacted by Ruy Adorno and Joshua
8. ruyadorno

   removed

   Agendawill be discussed at the Open RFC callwill be discussed at the Open RFC call

   on Oct 28, 2020
9. ruyadorno commented on Jan 26, 2022

   

   ruyadorno

   on Jan 26, 2022

   Contributor

   More actions

   Let's continue the conversation over here: #516
10. ruyadorno

    closed this as completedon Jan 26, 2022