v3.0.1

Changed

• Split runtime and development Node.js version requirements so the runtime floor is no longer inflated by dev-only tooling. engines.node (the version consumers need to run the CLI) is restored to >=18.17; the >=22.22.1 floor required by lint-staged@17 now lives in devEngines.runtime and applies only to contributors working on the source.

Full Changelog: v3.0.0...v3.0.1

v3.0.0

Changed

• BREAKING: Minimum Node.js version is now 22.22.1 (raised from 18.17), required by lint-staged@17.
• BREAKING: The CLI now connects to an externally managed LanguageTool HTTP service instead of managing the LanguageTool lifecycle locally. See MIGRATION.md for upgrade steps.
• BREAKING: Running the CLI interactively with no arguments now exits with code 1 (previously exited 0 silently). Scripts relying on the old silent no-op behavior must pass explicit input.
• An empty piped STDIN no longer triggers an HTTP request to the LanguageTool service; the CLI exits 0 immediately.
• All dependencies are now pinned to exact versions (caret ranges removed) for reproducible installs.

Added

• --help / -h prints usage and exits 0.
• --version / -V prints the package version and exits 0.
• --url / -u <url> overrides languageTool.url for a single invocation with the highest precedence (flag > user config > default).
• Usage is now printed when the CLI is run interactively with no input (no piped stdin and no file arguments).
• A warning is now emitted for each file argument that does not resolve to an existing path.

Removed

• The postinstall script that downloaded and unpacked a LanguageTool archive during installation.
• Automatic Java checks and local Java-based LanguageTool server startup.
• The project Dockerfile.
• simple-git-hooks, replaced by a native pre-commit hook in .githooks/. Contributors must run npm run enable-git-hooks once to activate it (git config core.hooksPath .githooks).

Full Changelog: v2.0.2...v3.0.0