SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

[PR #4845] [MERGED] Update package dependencies in package.json and package-lock.json #5305

New Issue
Closed
opened 2025-11-20 07:05:18 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 07:05:18 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/4845
Author: @jaainil
Created: 5/29/2025
Status: ✅ Merged
Merged: 5/30/2025
Merged by: @BramSuurdje

Base: main ← Head: main

📝 Commits (1)

  • c6f7721 Update package dependencies in package.json and package-lock.json

📊 Changes

2 files changed (+2405 additions, -1950 deletions)

View changed files

📝 frontend/package-lock.json (+2403 -1948)
📝 frontend/package.json (+2 -2)

📄 Description

  • Upgraded "next-themes" from ^0.3.0 to ^0.4.6
  • Upgraded "react-day-picker" from 8.10.1 to ^9.7.0
  • Updated various other dependencies to their latest versions for improved performance and security.

✍️ Description

Dependency Compatibility Fix for React 19

  • Upgraded "next-themes" from ^0.3.0 to ^0.4.6 to resolve React 19 compatibility issues
  • Upgraded "react-day-picker" from 8.10.1 to ^9.7.0 to resolve date-fns v4 compatibility issues

This fixes the ERESOLVE dependency conflicts that were preventing npm update from running successfully. Both packages now properly support the current React 19 and date-fns v4 versions used in the project.

Before: npm update failed with peer dependency conflicts
After: npm update and npm run dev work without issues

🔗 Related PR / Issue

Link: #

✅ Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • ✨ New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/community-scripts/ProxmoxVE/pull/4845 **Author:** [@jaainil](https://github.com/jaainil) **Created:** 5/29/2025 **Status:** ✅ Merged **Merged:** 5/30/2025 **Merged by:** [@BramSuurdje](https://github.com/BramSuurdje) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`c6f7721`](https://github.com/community-scripts/ProxmoxVE/commit/c6f7721cc6590e4f44c4f9d8ef6674e20ba70953) Update package dependencies in package.json and package-lock.json ### 📊 Changes **2 files changed** (+2405 additions, -1950 deletions) <details> <summary>View changed files</summary> 📝 `frontend/package-lock.json` (+2403 -1948) 📝 `frontend/package.json` (+2 -2) </details> ### 📄 Description - Upgraded "next-themes" from ^0.3.0 to ^0.4.6 - Upgraded "react-day-picker" from 8.10.1 to ^9.7.0 - Updated various other dependencies to their latest versions for improved performance and security. <!--🛑 New scripts must be submitted to [ProxmoxVED](https://github.com/community-scripts/ProxmoxVED) for testing. PRs without prior testing will be closed. --> ## ✍️ Description **Dependency Compatibility Fix for React 19** - Upgraded "next-themes" from ^0.3.0 to ^0.4.6 to resolve React 19 compatibility issues - Upgraded "react-day-picker" from 8.10.1 to ^9.7.0 to resolve date-fns v4 compatibility issues This fixes the `ERESOLVE` dependency conflicts that were preventing `npm update` from running successfully. Both packages now properly support the current React 19 and date-fns v4 versions used in the project. **Before:** `npm update` failed with peer dependency conflicts **After:** `npm update` and `npm run dev` work without issues ## 🔗 Related PR / Issue Link: # ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [x] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [x] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [ ] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2025-11-20 07:05:18 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#5305
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?