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
There are some packages that are clearly deprecated, such as flux, but they are not officially marked as deprecated via npm itself. As a result, tools that manage dependencies (like Renovate) can't detect or report these libraries and inform users that they should look for replacements.
The problem is that GitHub repositories are often in read-only mode (like the flux one), and the original authors have moved on to different projects or companies. This makes it difficult to ask them directly to properly deprecate their past work.
Is there a way that npmjs.com could deprecate such projects for the sake of clarity? Maybe you could offer extra drop-down entry for that on your support page? 🤔
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey folks!
There are some packages that are clearly deprecated, such as flux, but they are not officially marked as deprecated via npm itself. As a result, tools that manage dependencies (like Renovate) can't detect or report these libraries and inform users that they should look for replacements.
The problem is that GitHub repositories are often in read-only mode (like the flux one), and the original authors have moved on to different projects or companies. This makes it difficult to ask them directly to properly deprecate their past work.
Is there a way that npmjs.com could deprecate such projects for the sake of clarity? Maybe you could offer extra drop-down entry for that on your support page? 🤔
Beta Was this translation helpful? Give feedback.
All reactions