Deprecating packages

[benogle]

What's the story for deprecating a package? Say I am no longer developing my package, and I want to point to someone else's package.

The easiest thing is obviously putting something in the readme that points to another package. But deprecation would not be shown in the settings view unless the readme button were explicitly clicked.

[nathansobo]

A package.json field?

On Mon, Mar 10, 2014 at 7:09 PM, Ben Ogle notifications@github.com wrote:

What's the story for deprecating a package? Say I am no longer developing
my package, and I want to point to someone else's package.

The easiest thing is obviously putting something in the readme that points
to another package. But deprecation would not be shown in the settings view
unless the readme button were explicitly clicked.

Reply to this email directly or view it on GitHubhttps://github.com//issues/74
.

[kevinsawicki]

Yeah, npm already has a field for this I believe and it logs a warning when you install a deprecated package.

https://www.npmjs.org/doc/cli/npm-deprecate.html