Fix dependency compatibility for VS Code 1.74/Node 20 and migrate to Husky 9

[jsldvr]

Fix dependency compatibility for VS Code 1.74/Node 20 and migrate to Husky 9

Description

Fixes a set of dependency-compatibility issues that broke packaging on Node 20 / VS Code 1.74, and migrates the Husky setup off the deprecated Husky 8 bootstrap.

• @types/vscode exact-pinned to 1.74.0 (was ^1.74.0, which had silently drifted to resolve a newer version in the lockfile, exceeding the engines.vscode: ^1.74.0 baseline).
• @vscode/vsce bumped to ^3.9.2 and fs-extra bumped to ^11.4.0, each verified independently and combined against compile/test/packaging before being kept.
• @vscode/test-electron left unchanged at ^3.0.0 to avoid a Node 22 requirement introduced in 3.1.0.
• husky bumped to 9.1.7; the prepare script now runs husky instead of the deprecated husky install; .husky/pre-commit no longer sources the removed husky.sh shim.
• package-lock.json regenerated with npm 10.8.2 to match the resolver CI actually uses, preserving the correct nested @types/node typings used by Stryker's Inquirer prompts without changing the project's root @types/node (still 16.x).

This supersedes #1 (grouped dependency bump) and #3 (Husky 9 bump), both closed in favor of this PR.

PR Checklist

• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My code follows the code style of this project.
• I ran the lint checks which produced no new errors nor warnings for my changes.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.

Does This Introduce a Breaking Change?

No. All changes are development tooling and packaging dependencies (types, bundler, git hooks); no src/ application code changed.

Testing

• Instructions for testing and validation of your code:
  • npm ci (npm 10.8.2, matching CI), npm ls --all, npm run compile, npm run lint, npm run test:unit (48 passing), npm run package:win32-x64 — all run locally, all passed.
  • Full Node 20 CI matrix on this PR (build-and-unit-test + all 7 package-platform-targets) — all green.
  • sh .husky/pre-commit sanity run with an empty stage, confirming the typecheck → lint-staged sequence still executes correctly after the Husky 9 migration.

Any Relevant Logs or Outputs

TBD

Other Information or Known Dependencies

• The VSIX now bundles more files under .husky/_ (18 vs. 3 previously) since .vscodeignore doesn't exclude .husky/ and Husky 9 generates more internal hook stub files than Husky 8 did. Trivial size impact; left as a possible follow-up if you want it trimmed via .vscodeignore.
• PR Bump typescript from 4.9.5 to 7.0.2 #2 (TypeScript 7), Bump lint-staged from 13.2.3 to 17.2.0 #4 (lint-staged 17), and Bump @types/node from 16.18.126 to 26.1.1 #5 (@types/node 26) were closed separately as wontfix via Dependabot ignore commands; not part of this PR.

[Copilot]

Pull request overview

This PR updates the VS Code extension’s dependency set to better align with VS Code ^1.74.0 and modern Node toolchains, and migrates the repo’s Git hook setup to Husky 9.

Changes:

• Migrated Husky setup to v9 (updated prepare script and Husky dependency).
• Pinned @types/vscode to 1.74.0 and updated packaging/tooling dependencies (@vscode/vsce, transitive deps).
• Updated runtime dependency fs-extra to ^11.4.0.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
package.json	Updates Husky prepare script, pins @types/vscode to 1.74.0, and bumps several dependencies.
package-lock.json	Locks updated dependency graph reflecting Husky/vsce/fs-extra updates.
.husky/pre-commit	Adjusts the pre-commit hook content for the Husky migration.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.