You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to enable/disable email notifications for specific package managers. For example, I have a Javascript project where the source code contains 1 dependency in bower.json and ~20 dependencies in package.json. Libraries.io is tracking 806(!) dependencies for this project, the vast majority of which are being pulled from the yarn.lock file as transitive dependencies.
While I find the emails regarding updates to my direct dependencies to be extremely useful, email notifications for these several hundred transitive dependencies are much less so. If I could turn off email notifications from libraries.io for Yarn while leaving them enabled for Bower and NPM, then the signal to noise ratio for these emails would dramatically increase for me.
I propose adding the ability to turn emails on/off by package manager, as this seems like the clearest line to draw for common use cases such as NPM/Yarn.
The text was updated successfully, but these errors were encountered:
It would be nice to be able to enable/disable email notifications for specific package managers. For example, I have a Javascript project where the source code contains 1 dependency in
bower.json
and ~20 dependencies inpackage.json
. Libraries.io is tracking 806(!) dependencies for this project, the vast majority of which are being pulled from theyarn.lock
file as transitive dependencies.While I find the emails regarding updates to my direct dependencies to be extremely useful, email notifications for these several hundred transitive dependencies are much less so. If I could turn off email notifications from libraries.io for Yarn while leaving them enabled for Bower and NPM, then the signal to noise ratio for these emails would dramatically increase for me.
I propose adding the ability to turn emails on/off by package manager, as this seems like the clearest line to draw for common use cases such as NPM/Yarn.
The text was updated successfully, but these errors were encountered: