v2.3.0

This package is now deployed with provenance.

Dependencies have been updated.

Full Changelog: v2.2.0...v2.3.0

v2.2.0

New feature: Recursive scanning. Thanks, @sunshineo! (#3)

You can now use the --levels/-l option to specify the number of levels (depth) to go down the dependency tree.

v2.1.0

Now using release date of latest version instead of modified date (88567cc)

The time.modified field is apparently not the time of the latest release, it can be much more recent. I have not found any good documentation on exactly what "modified" means.

I think using the most recent release date is the best measure for detecting if a package is ditched or not. Note that this does not mean
the version tagged with the "latest" tag - this will also consider other tags, like rc, alpha, next, etc.

v2.0.1

Fixed off-by-one error in month part of date:

v2.0.0

Breaking Changes

• Minimum required Node version is now 12, though older versions might work.
• The default number of days needed for flagging a package as ditched is increased from 90 to 365.
• Removed console.logs 'Looking for ...' and 'Found X packages."
• There is now no output if no packages to show (previously the table was printed with headers only).
• The actual date of the latest release is added to the table.

New Features

• Option --days/-d for setting number of days needed to flag a package as ditched.
• Flag --version for showing the package's info.
• Flag --help for showing usage info.

Internal

• Project is converted to TypeScript
• yargs is used for parsing command line arguments

v1.0.2

Don't crash entire program if it fails to get info for one package

For instance, if using private or local packages that are not in the npm registry, the entire program would fail. Now it treats these as not ditched, or if using --all, it will print a line saying no info was found.

v1.0.1

The postinstall script would make the installation of ditched fail. Also, the script in package.json had the wrong name. Both fixed now!

v1.0.0

This is the first release of this fork of abandoned and here's what's different from abandoned v0.1.0.

Functional differences

• Only ditched packages are listed by default. If you want also non-ditched packages to be listed, use the --all flag.
• If there are any ditched dependencies, the process will exit with an error code (1)

Improvements

• The async dependency is removed. Native async/await is used instead, requiring at least Node v8.
• The request dependency is removed. The core https lib is used instead.
• Remaining dependencies are updated to their latest versions.