Features
feat: Add `--force-check` cli option (#9080)
feat: Add --force-check cli option (#9080)
This pull request introduces a new --force-check option to the CLI, allowing users to force specific files to be checked even if they would normally be excluded. It also standardizes dependency configuration naming, improves error handling and reporting for the CLI, and updates TypeScript target versions in config files. The most important changes are grouped below.
New CLI Feature: Force Check
- Added a
--force-checkoption to thelintcommand, allowing files specified with--file,--files, or--file-listto be checked even if they would normally be excluded. This includes updates to the CLI interface, validation logic, and documentation/help output. [1] [2] [3] [4] [5] - Implemented logic in the file determination and processing flow to honor the
forceCheckflag, ensuring excluded files can be checked when requested, and updated reporting of skipped files. [1] [2] [3] [4] [5] [6]
CLI Error Handling and Testing
- Improved error handling for invalid combinations of CLI options (e.g., using
--force-checkwithout specifying files, or mixing globs and--file), with corresponding error messages and test cases. [1] [2] - Enhanced test coverage for the new
--force-checkoption, including snapshot updates for help and error outputs. [1] [2] [3] [4] [5] [6] [7]
Dependency Configuration Standardization
- Renamed the dependency configuration property from
onlyAllowBundletoonlyBundleacross all relevant config files and documentation for consistency. [1] [2] [3] [4]
Other Improvements
- Updated TypeScript target version in default config from
Node20toNode22. - Improved CLI process exit code handling for error scenarios.
- Minor improvement to CLI reporter logic to avoid emitting empty results.
- Cleaned up and simplified the coverage collection script in
package.json.
Fixes
fix: Updated package.json exports (#8965)
fix: Updated package.json exports (#8965)
This fixes a few package exports that were wrong or inconsistent (e.g. exports["."] not the same path as main).
The pnpm test script was failing locally due to my ~/.npmrc having ignore-scripts=true, which prevented the preinstall script from running. I updated test:prep to call the preinstall script, which should be fast if you already have yarn installed.
Dictionary Updates
fix: Workflow Bot -- Update Dictionaries (main) (#9067)
fix: Workflow Bot -- Update Dictionaries (main) (#9067)
Update Dictionaries (main)
Summary
.../snapshots/django/django/report.yaml | 82 ++++++++++------------
.../snapshots/django/django/snapshot.txt | 51 ++++++--------
packages/cspell-bundled-dicts/package.json | 6 +-
pnpm-lock.yaml | 30 +++++---
4 files changed, 84 insertions(+), 85 deletions(-)