chore(deps): bump cspell from 9.8.0 to 10.0.0

[dependabot]

Bumps cspell from 9.8.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)
• See full diff in compare view

[cloudflare-workers-and-pages]

Deploying frameworks with    Cloudflare Pages

Latest commit:	daad42d
Status:	✅  Deploy successful!
Preview URL:	https://f64fc517.frameworks-573.pages.dev
Branch Preview URL:	https://dependabot-npm-and-yarn-deve-lsud.frameworks-573.pages.dev

View logs

[frameworks-volunteer]

Model: z-ai/glm-5.1 Reasoning: medium Provider: openrouter

Security: Clean. No secrets, injection vectors, or suspicious packages. All changes are within the @cspell/* ecosystem plus import-fresh v3->v4, semver 7.7.4->7.8.1, and removal of unused transitive deps (callsites, clear-module, parent-module, resolve-from@4).

QA: Diff matches description. Lint check passes. Two observations:

1. Node.js engine floor raised from >=20 to >=22.18.0. This is the major breaking change in cspell v10 (drops Node 20 support). The repo's preview-build.yml already uses Node 22, so GHA workflows are compatible. However, the Cloudflare Pages build failed -- likely because Pages defaults to an older Node version. The Pages project may need NODE_VERSION=22 set in its environment settings, or the build command may need to fail gracefully if cspell is only a dev dependency and not needed for the Pages build itself.

2. The spell-check workflow (spell-check.yml) runs on main only, so this PR won't trigger it. When this reaches main, the npx cspell call will work fine since GHA ubuntu-latest can run Node 22+.

No blocking issues in the code change itself. The Cloudflare Pages failure is an environment configuration concern that the maintainers should verify before merging.

[scode2277]

All good here, the Claudflare run was failing for an incident they had on the 25th and the Node version we use is already >20 (as also vocs required it months ago).

Anyway, reviewing this, surfaced a small config improvement needed for the spell-check setup. Tracking it separately and will land it asap.

GTG @mattaereal!