Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Package deprecation notice #56

Open
ghost opened this issue Jul 22, 2015 · 5 comments
Open

Package deprecation notice #56

ghost opened this issue Jul 22, 2015 · 5 comments

Comments

@ghost
Copy link

ghost commented Jul 22, 2015

Could the update-notifier package also post a console update notification when a CLI tool has been deprecated using npm's deprecate command?

@arthurvr
Copy link

IMHO this is out of scope for this module.

@ghost
Copy link
Author

ghost commented Jul 22, 2015

Is it out of scope to print the deprecation notice for a CLI tool that is simply out of date, when the out of date version has been deprecated. Especially if the deprecation notice contains text like npm's example: critical bug fixed in v0.2.3

This seems like critical information we should be disseminating to consumers of these CLI tools.

@sindresorhus
Copy link
Owner

I think it's a great idea. PR welcome :)

@robbbz
Copy link

robbbz commented Jul 22, 2015

Can we make this a separate module? I can see apps where I wouldn't want update notifications but I do want notifications when it's deprecated.

@ghost
Copy link
Author

ghost commented Jul 29, 2015

@sindresorhus based on @robbbz comment, what do you think?

I am still in favor of update-notifier providing deprecation notices under the run npm text. I'm also fine with having a separate package that will just retrieve the deprecation notice of a particular package at a particular version (kind of like the helper package latest-version).

However, should we also have a deprecation-notifier package that provides similar functionality to update-notifier?

@sindresorhus sindresorhus changed the title Package Deprecation Notice Package deprecation notice Jun 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants