starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Resolve peer dependencies when running npm install #567

New Issue
Closed
opened 2026-02-04 19:53:39 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-04 19:53:39 +03:00
Owner
Copy Link

Originally created by @scallaway on GitHub (Mar 1, 2025).

Originally assigned to: @BramSuurdje on GitHub.

📌 Task summary

Resolve Frontend peer dependencies

📋 Task details

Didn't think this classed as a bug since it's not user-facing, but spotted this when I cloned the repo the other day to work on a different bug.

If you try and run npm install in /frontend, you're met with a wash of NPM errors in the console complaining about unresolvable peer dependencies.

You are able to get around this by running npm install -f, but that doesn't feel like a very long-term solution (and isn't very accessible for other devs).

Solving this would make the path to getting a local dev environment setup for the repository much nicer.

Originally created by @scallaway on GitHub (Mar 1, 2025). Originally assigned to: @BramSuurdje on GitHub. ### 📌 Task summary Resolve Frontend peer dependencies ### 📋 Task details Didn't think this classed as a bug since it's not user-facing, but spotted this when I cloned the repo the other day to work on a different bug. If you try and run `npm install` in `/frontend`, you're met with a wash of NPM errors in the console complaining about unresolvable peer dependencies. You are able to get around this by running `npm install -f`, but that doesn't feel like a very long-term solution (and isn't very accessible for other devs). Solving this would make the path to getting a local dev environment setup for the repository much nicer.
OVERLORD added the website label 2026-02-04 19:53:39 +03:00
OVERLORD commented 2026-02-04 19:53:52 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 1, 2025):

Frontend will be completly new build by @BramSuurdje in next time

@MickLesk commented on GitHub (Mar 1, 2025): Frontend will be completly new build by @BramSuurdje in next time
OVERLORD commented 2026-02-04 19:54:07 +03:00
Author
Owner
Copy Link

@BramSuurdje commented on GitHub (Mar 2, 2025):

i normally use bun so i don't have this issue, thank you for bringing it up to me though.

@BramSuurdje commented on GitHub (Mar 2, 2025): i normally use bun so i don't have this issue, thank you for bringing it up to me though.
OVERLORD commented 2026-02-04 19:54:19 +03:00
Author
Owner
Copy Link

@scallaway commented on GitHub (Mar 2, 2025):

I didn't see any documentation - although I didn't look very hard - on what tooling the project used so based my guess on the fact that there's a package-lock.json file (as opposed to a yarn.lock etc.).

I haven't tried using Bun here!

@scallaway commented on GitHub (Mar 2, 2025): I didn't see any documentation - although I didn't look very hard - on what tooling the project used so based my guess on the fact that there's a `package-lock.json` file (as opposed to a `yarn.lock` etc.). I haven't tried using Bun here!
OVERLORD commented 2026-02-04 19:54:29 +03:00
Author
Owner
Copy Link

@scallaway commented on GitHub (Mar 2, 2025):

Although, have just tried and yeah bun resolves everything without any issue. In that case, I think swapping over to a bun.lockb file and specifying the project primarily uses bun is probably the way forward here.

@scallaway commented on GitHub (Mar 2, 2025): Although, have just tried and yeah `bun` resolves everything without any issue. In that case, I think swapping over to a `bun.lockb` file and specifying the project primarily uses `bun` is probably the way forward here.
OVERLORD commented 2026-02-04 19:54:37 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Mar 20, 2025):

set to internal roadmap for rebuild web-frontend

@MickLesk commented on GitHub (Mar 20, 2025): set to internal roadmap for rebuild web-frontend
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label website
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#567
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?