v4

[duniul]

Lots of fundamental CLI changes as well as a few breaking changes, plus lots of bug fixes. Removes most secondary dependencies and optimizes the bundle.

4.0.0

Major Changes

• BREAKING analyze() now returns { files, failures } instead of an array of per-file results. bc65618 @duniul
• BREAKING Package is now ESM only. CLI usage works the same as before, but breaks CJS usage of the programmatic API. ac6de03 @duniul
• BREAKING Minimum supported Node version is now v22. 6fd8cde @duniul

Minor Changes

• Update picomatch dependency to v4. 00c3cd6 @duniul
• Surface non-fatal filesystem failures instead of swallowing them silently. bc65618 @duniul
• Add new --fail-on-error flag which exits with a non-zero status code when any failure is recorded. Exit code stays 0 by default, matching prior behavior. bc65618 @duniul

Patch Changes

• Remove potentially unsafe doc/ and docs/ from default patterns. 293e149 @duniul
• Remove pretty-bytes, pretty-ms, supports-color, and clipanion dependencies. d428e34 61b97e7 dfb87bc @duniul
• Replace clipanion with Node's built-in parseArgs for CLI args parsing. 61b97e7 dfb87bc @duniul
• Clearly indicate which steps were skipped in --dry-run output. c3bd4b2 @duniul
• Set "sideEffects": false in package.json. f67c2c9 @duniul
• Fix repository definition in package.json. 47b01ae @duniul
• Fix the default hint shown for the --directory option. b44d0ef @duniul
• Fix globs not starting with / being incorrectly prefixed with an extra **. 34a3b27 @duniul
• Ensure --keep-empty is respected by clean command. 695f83e @duniul
• Skip confirmation prompt in CI/without TTY, require --yes or -y. b0a1838 @duniul
• Avoid parsing default globs twice in analyze. 6f878df @duniul
• Avoid redundant readdir calls when removing empty parent directories. 540c372 @duniul
• Update minor dependency versions. 7491637 @duniul
• Update the default file patterns. 9ab2ba3 @duniul

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f76b9c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR