chore(deps-dev): bump cspell from 9.7.0 to 10.0.0

[dependabot]

Bumps cspell from 9.7.0 to 10.0.0.

Release notes

Sourced from cspell's releases.

v10.0.0

Features

fix: upgrade import-fresh from v3 to v4 (#8786)

Summary

Upgrades import-fresh from v3 to v4.

API changes in v4

• v3: Synchronous default export — importFresh(modulePath) returns the module directly
• v4: Factory pattern — createImportFresh(parentURL) returns an async function; v4 is ESM-only and uses Node.js module loader hooks instead of manipulating the require cache

Changes

• packages/cspell-lib/package.json: bump import-fresh to ^4.0.0; remove clear-module dependency (no longer needed since v4 uses module loader hooks instead of Node's require cache)
• packages/cspell-lib/src/lib/Settings/Controller/pnpLoader.ts:
  • Import createImportFresh factory; call createImportFresh(pnpFileUrl) at use time inside loadPnp(), bound to the pnp file's own URL so each load is correctly scoped to the file being loaded
  • Make loadPnp and loadPnpIfNeeded async
  • Change cachedPnpImportsSync → cachedPnpImports (now stores Promise<LoaderResult>)
  • Remove clearModule.single usage (v4 cache-busts via loader hooks; clearing the require cache is no longer applicable)
  • Pass a file URL (toFileUrl(pnpFile).href) to importFresh since v4 uses import() under the hood, which requires URLs or relative specifiers for absolute paths
  • Use optional chaining on the module's default export to handle edge cases
• test-packages/cspell-lib/test-cspell-lib-rollup/package.json: bump import-fresh to ^4.0.0
• test-packages/cspell-lib/test-cspell-lib-webpack/package.json: bump import-fresh to ^4.0.0

Testing

All 91 test files (1584 tests) pass, including the 10 dedicated pnpLoader tests.

---

feat!: Drop support for Node 20 (#8779)

Pull request overview

This PR updates the monorepo to require Node.js 22.18+ (dropping Node 20 support), aligning package engine constraints, CI matrices, and documentation with the new baseline.

Changes:

• Bump engines.node across packages/test-packages to >=22.18.0 and update root @types/node to ^22.19.15.
• Update CI workflows to test Node 22/24/25 and adjust integration update workflow to Node 22.
• Remove eslint-plugin-n “unsupported node builtins” disables now that the minimum Node version includes those built-ins.

... (truncated)

Changelog

Sourced from cspell's changelog.

v10.0.0 (2026-04-06)

Features

fix: upgrade import-fresh from v3 to v4 (#8786)

Summary

Upgrades import-fresh from v3 to v4.

API changes in v4

• v3: Synchronous default export — importFresh(modulePath) returns the module directly
• v4: Factory pattern — createImportFresh(parentURL) returns an async function; v4 is ESM-only and uses Node.js module loader hooks instead of manipulating the require cache

Changes

• packages/cspell-lib/package.json: bump import-fresh to ^4.0.0; remove clear-module dependency (no longer needed since v4 uses module loader hooks instead of Node's require cache)
• packages/cspell-lib/src/lib/Settings/Controller/pnpLoader.ts:
  • Import createImportFresh factory; call createImportFresh(pnpFileUrl) at use time inside loadPnp(), bound to the pnp file's own URL so each load is correctly scoped to the file being loaded
  • Make loadPnp and loadPnpIfNeeded async
  • Change cachedPnpImportsSync → cachedPnpImports (now stores Promise<LoaderResult>)
  • Remove clearModule.single usage (v4 cache-busts via loader hooks; clearing the require cache is no longer applicable)
  • Pass a file URL (toFileUrl(pnpFile).href) to importFresh since v4 uses import() under the hood, which requires URLs or relative specifiers for absolute paths
  • Use optional chaining on the module's default export to handle edge cases
• test-packages/cspell-lib/test-cspell-lib-rollup/package.json: bump import-fresh to ^4.0.0
• test-packages/cspell-lib/test-cspell-lib-webpack/package.json: bump import-fresh to ^4.0.0

Testing

All 91 test files (1584 tests) pass, including the 10 dedicated pnpLoader tests.

---

feat!: Drop support for Node 20 (#8779)

Pull request overview

This PR updates the monorepo to require Node.js 22.18+ (dropping Node 20 support), aligning package engine constraints, CI matrices, and documentation with the new baseline.

Changes:

... (truncated)

Commits

• 6ddfd57 v10.0.0
• 9ab431c chore: Prepare Release v10.0.0 (auto-deploy) (#8781)
• ef406ee feat!: Drop support for Node 20 (#8779)
• c822013 v9.8.0
• ff063b5 chore: Prepare Release v9.8.0 (auto-deploy) (#8639)
• 34c89f7 chore: clean up imports (#8752)
• c1a4143 chore: bump flatted from 3.4.1 to 3.4.2 (#8724)
• 03cf1c4 chore: Update tsdown to 0.21 (#8691)
• ee39fb6 chore: bump the production-dependencies group across 1 directory with 7 updat...
• a9d7eef fix: Workflow Bot -- Update Dictionaries (main) (#8688)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: b671734

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