-
Notifications
You must be signed in to change notification settings - Fork 0
fix: vulnerable dependencies in repo #11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -11,20 +11,24 @@ | |||||
| "type-check": "tsc --noEmit" | ||||||
| }, | ||||||
| "devDependencies": { | ||||||
| "@marp-team/marp-cli": "^4.2.3", | ||||||
| "@marp-team/marp-cli": "^4.3.1", | ||||||
| "@types/node": "^24.10.1", | ||||||
| "husky": "^9.1.7", | ||||||
| "js-yaml": "^4.1.1", | ||||||
| "lint-staged": "^16.2.6", | ||||||
| "prettier": "^3.6.2", | ||||||
| "tar-fs": "^3.1.1", | ||||||
| "tsx": "^4.20.6", | ||||||
| "lint-staged": "^16.4.0", | ||||||
| "prettier": "^3.8.1", | ||||||
| "tar-fs": "^3.1.2", | ||||||
| "tsx": "^4.21.0", | ||||||
| "typescript": "^5.9.3", | ||||||
| "vite": "^8.0.0", | ||||||
| "vitest": "^4.1.0" | ||||||
| "vite": "^8.0.3", | ||||||
| "vitest": "^4.1.2" | ||||||
| }, | ||||||
| "lint-staged": { | ||||||
| "*": "prettier --write --ignore-unknown" | ||||||
| }, | ||||||
| "pnpm": { | ||||||
| "overrides": { | ||||||
| "@xmldom/xmldom": ">=0.9.9" | ||||||
|
||||||
| "@xmldom/xmldom": ">=0.9.9" | |
| "@xmldom/xmldom": ">=0.9.9 <1.0.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The updated toolchain (notably vite@8.0.3 and lint-staged@16.4.0) has stricter Node.js engine requirements (vite requires >=20.19.0, lint-staged requires >=20.17). package.json currently doesn’t declare an engines.node range, so contributors/CI running an older Node 20.x patch can hit install/runtime failures. Consider adding an explicit "engines": {"node": ">=20.19.0"} (or whichever minimum you intend) and aligning CI/local tooling to that minimum.