Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@
"@types/semver": "^7.7.0",
"@types/xml2js": "^0.4.14",
"@types/yargs": "^17.0.33",
"eslint": "10.8.1",
"eslint": "10.10.0",
"eslint-config-prettier": "^10.1.8",
"globals": "^17.7.0",
"husky": "^9.1.7",
Expand All @@ -59,12 +59,12 @@
"prettier": "3.9.6",
"ts-add-js-extension": "^1.6.6",
"typescript": "^6.0.3",
"typescript-eslint": "8.67.0",
"typescript-eslint": "8.69.0",
"vite": "^8.2.1",
"vitest": "^4.1.0"
"vitest": "^5.0.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Align Vitest with the declared Node support range

When developing on Node 22.0–22.11 (or Node 23/25), package.json still declares the runtime supported via node >=22.0.0, but this upgrade selects Vitest 5, whose lockfile engine is ^22.12.0 || ^24.0.0 || >=26.0.0. The documented install/test workflow therefore has no supported test runner on part of the project's advertised Node range and can be rejected outright when engine-strict is enabled; either retain Vitest 4 or raise and synchronize the minimum Node requirement.

AGENTS.md reference: AGENTS.md:L11-L17

Useful? React with 👍 / 👎.

},
"dependencies": {
"@napi-rs/keyring": "^1.2.0",
"@napi-rs/keyring": "^2.0.0",
"chalk": "^6.0.0",
"dotenv": "^17.4.2",
"escape-html": "^1.0.3",
Expand Down
Loading