v0.18.4

v0.18.4

v0.18.3

v0.18.3

v0.18.2

v0.18.2

v0.18.1

v0.18.1

v0.16.0: Implement human-readable `Display` for UnusedFinderReport (#79)

Implements a human-readable `Display` for UnusedFinderReport.

---------

Co-authored-by: Max Huang-Hobbs <[email protected]>

v0.15.0

applying package updates

v0.14.2: add report_exported_items flag to gate reporting exported items (#77)

Disable per-item reporting with report_exported_items flag

This is for cleaner test reporting while debugging unused files in
`unused_bin`

---------

Co-authored-by: Max Huang-Hobbs <[email protected]>

v0.14.1: Massive un-reviewable project restructuring (#76)

This change decomposes the project from a single crate into a number of
crates. The decomposition is not complete, but it's enough to extract
unused_finder as a separate library from good_fences.

The motivation for this change is to allow debugging unused_finder with
LLDB without linking against `node`. before this change, any code that
referenced `napi` would require linking against `node`, which is
difficult to implement in vscode's development tooling. Instead, this
change restructures the code so that subsets of it can be compiled and
executed without linking against node, for the sake of debugging that
functionality.

In this case, `unused_bin` is introduced as a CLI entrypoint to
`unused_finder`, used only for debugging it against a project. The
launch configuration in `.vscode/launch.json` is set up to run
`unused_bin` with against some on-disk `--config-path` argument, which
is expected to be manually confiured by the user, or generated by
project-specific build tooling.

---------

Co-authored-by: Max Huang-Hobbs <[email protected]>

v0.14.0: update yarn + cargo (#75)

Updates yarn & cargo

---------

Co-authored-by: Max Huang-Hobbs <[email protected]>

v0.13.2

Fixed issue preventing unused-finder work on newly-created codespaces…