consider removing update-notifier? #2768
Replies: 2 comments 8 replies
-
Thanks for the feedback. Minimizing (transitive) dependencies is not a goal of this project. We do want people to upgrade, especially within teams where folks should remain on the same point release to avoid compatibility issues. |
Beta Was this translation helpful? Give feedback.
-
Please consider this! I'm currently looking into switching away from Ava because of this. Updating the dependency should not be the responsibility of the dependency itself. For anybody also looking around this awesome list seems to contain some interesting options: https://github.com/talentlessguy/awesome-node-esm#testing |
Beta Was this translation helpful? Give feedback.
-
... to reduce dependencies and increase speed
Considering all the kind of packages that is being installed for just getting update notification is not so much worth it IMO.
https://npm.anvaka.com/#/view/2d/update-notifier
quite a few have have dependa bot or similar in there workflow and use of ^, * and ~ to makes it less important
also every time a ci workflow happens it needs to download all this packages in vain.
Time to install only update-notifier in a empty project:
created 1 461 708 byte (3,2 MB on drive) for 703 files
npm added 91 packages, and audited 92 packages in 17s
This is not something everyone wants to have in there workflow/pipeline. it's non essential
More afraid that any of this 91 sub dependencies gets a vulnerability (like it already did once: #2182)
Beta Was this translation helpful? Give feedback.
All reactions