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
As far as I can tell, when mrt installing a deprecated package, perhaps from inherited codebase, the user has no indication that a package is deprecated. Right now, the only way to check that a package might be deprecated is to look at its README.
Does meteorite/MDG have plans for a "deprecated" flag that would warn on install, and perhaps point to an alternative package, or a resource for more information?
The text was updated successfully, but these errors were encountered:
My understanding is that packages will be explicitly tied to meteor versions that they have been marked to work with. So deprecation will happen implicitly when an author fails to keep the package up to date with new versions.
We'll find out more at devshop this month I guess :)
Good point. The deprecation use case I had in mind was when an author wants their package to stop being used on purpose, e.g. because a better package has emerged.
As far as I can tell, when
mrt install
ing a deprecated package, perhaps from inherited codebase, the user has no indication that a package is deprecated. Right now, the only way to check that a package might be deprecated is to look at its README.Does meteorite/MDG have plans for a "deprecated" flag that would warn on install, and perhaps point to an alternative package, or a resource for more information?
The text was updated successfully, but these errors were encountered: