Skip to content

chore(deps-dev): bump the frontend-development group with 2 updates #343

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.

Sign up for GitHub

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

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps-dev): bump the frontend-development group with 2 updates #343

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,9 +52,9 @@
"@types/react": "^19.2.18",
"@types/react-dom": "^19.2.7",
"@vitejs/plugin-react": "^6.1.1",
"jsdom": "^28.1.0",
"jsdom": "^30.0.1",

@chatgpt-codex-connector chatgpt-codex-connector Bot Sep 13, 2026

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 Keep jsdom within the declared Node range

When contributors use Node 22.12–22.22.1 or Node 24.0–24.14, which are permitted by package.json's >=22.12 <25 engine and the README's Node 22/24 prerequisite, this upgrade installs a jsdom release whose lock metadata requires ^22.22.2 || ^24.15.0 || >=26.0.0. The pinned CI version (24.18) hides the mismatch, but supported local environments can reject the dependency or run the jsdom-backed Vitest suite on an unsupported runtime; either retain a compatible jsdom version or raise the repository's Node floor consistently.

Useful? React with 👍 / 👎.

"typescript": "^7.0.2",
"vite": "^8.2.2",
"vite": "^8.3.0",
"vitest": "^5.0.0",
"yaml": "2.9.0"
}
Expand Down
Loading
Loading