v0.13.2: Fixed issue preventing unused-finder work on newly-created codespaces…

… (#73)

v0.13.1: Fix UnusedFinder struct not using in-memory representation (#72)

Fixed unused finder struct not using memory representation of graph
containing entry packages/files as initial frontier.

v0.13.0: Reverted good-fences resolver function to enable run quick checks on …

…local environments (#71)

Current SWC resolver prioritizes resolving paths to `**/lib/**` files
instead of using tsconfig.paths.json `compilerOptions.paths` values.
This prevents devs from running good-fences accurately if they run local
builds or run `yarn typecheck` since those generate files under packages
`lib/` dir.
Reverting to old resolver and adding some logic to handle cases such as
adding extensions to files and appending `index` whenever is needed.

v0.12.0

Added anyhow and thiserror to do better error handling (#69)

v0.11.0: Added napi configuration triples additional property (#68)

Added triples additional property

v0.10.0: Address comments from PR #64 (#65)

Addresses @Adjective-Object 's comments from #64 

- Adds comments to `UnusedFinder::refresh_*` methods.
- Removes redundant property `UnusedFinder::flattened_walk_file_data` to
avoid information to not be synced in `UnusedFinder::graph`
- Improves validation for max_iteration in bfs_step/frontier execution.

v0.9.0: Added struct/class to run unused finder tool with in memory represent…

…ation (#64)

To run unused finder tool within a vscode extension some changes were
needed:
- To run tool on file save, a way to preserve the metadata of source
files done during file walk was needed
- An in-memory representation of files was created as a property of
`UnusedFinder` struct.
- Every-time we need to run the tool on an existing file, instead of
reading all files from disk, we just read from disk the last written
file and the rest is used from in-memory metadata from the original
file-walk or from previous iteration.

v0.8.0: Added report struct to improve error handling in owa-build (#63)

Created `UnusedFinderReport` struct:
- Instead of returning a `Vec<String>` that represents all error
messages thrown during execution, now return `UnusedFinderReport`
- `UnusedFinderReport::unused_files` a vec of files marked as unused,
this list is already sanitized and does not contain non-scanned files or
files that match any patter in `.unusedignore` file.
- `UnusedFinderReport::unused_files_items` hashmap with **_key: file
path_** and **_value: items within file that are not imported_**.

v0.7.0: Added support for `.unusedignore` file (#62)

Looks in cwd for a file called `.unusedignore`

Allowed items can be:
- specific file paths like
`shared/internal/owa-react-hooks/src/useWhyDidYouUpdate.ts`
- glob patterns (similar to a `.gitignore` wildcard patterns)
`shared/internal/owa-datetime-formatters/**`

v0.6.1: enable find unused items within files (#60)

- Added feature to track unused items within used files.
- When building report now filter used files and pull the ones that have
non-empty list inside `GraphFile::unused_items`.
- Added capability to track items masked through `export ... from ...`
statements.
- Resolve/Mark items as used inside `GraphFile` now return an enum if
the item was created in the file or it was pulled via export/from
statement.