Option to ignore deprecated versions

[ghost]

• I have read the list of known issues before filing this issue.
• I have searched for similiar issues before filing this issue.

• node version: 12.13.0
• npm version: 6.12.0
• npm-check-updates version: 4.0.1

---

Sometimes package authors release a new version by mistake and they mark such release as deprecated. For example: https://www.npmjs.com/package/primeng?activeTab=versions

But npm-check-updates still suggests to update to the latest version:

Can anything be done about it?

[raineorshine]

The deprecation status is retrieved with pacote:

$ pacote packument primeng | grep deprecated
      "deprecated": "Invalid configuration, use primeng-lts@8.1.3 instead"
      "deprecated": "Invalid configuration, use primeng-lts@8.1.x instead"

Which is what npm-check-updates uses to fetch package data.

So, yes, deprecated versions could be ignored if the deprecated field was checked.

[raineorshine]

It's probably a good practice for package authors to update their latest tag to a non-deprecated version.

Still, I don't see any downside to ncu printing a message and filtering deprecated versions out if one is detected.

[Jaimeloeuf]

Hey @raineorshine thanks for the explanation for this, but is there any updates on this? Since jkbrzt/rrule#417 issues like this still happen fairly frequently, it would be great if this package ignores the deprecated versions by default!

[raineorshine]

Fixed and published in v9.0.0.