[PR #9100] [MERGED] PeaNUT: use clean install flag during update #7827

New issue

Closed

opened 2026-02-26 16:30:51 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 16:30:51 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/9100
Author: @vhsdream
Created: 11/12/2025
Status: ✅ Merged
Merged: 11/12/2025
Merged by: @CrazyWolf13

Base: main ← Head: peanut-cleaninstall

📝 Commits (1)

67b52db PeaNUT: use clean install flag during update

📊 Changes

1 file changed (+2 additions, -2 deletions)

View changed files

📝 ct/peanut.sh (+2 -2)

📄 Description

✍️ Description

Fixes an issue with middleware update
also removed semicolon from tags

When running update in the LXC console, I encountered this error:

> peanut@5.17.0 build
> next build

   ▲ Next.js 16.0.1 (Turbopack)


> Build error occurred
Error: Both middleware file "./src/src/middleware.ts" and proxy file "./src/src/proxy.ts" are detected. Please use "./src/src/proxy.ts" only. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy
    at ignore-listed frames
 ELIFECYCLE  Command failed with exit code 1.

[ERROR] in line 43: exit code 0: while executing command $STD pnpm run build:local

I assumed it was because something was changed upstream but the app directory wasn't cleaned during install. Adding CLEAN_INSTALL=1 solved the issue for me.

✅ 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/9100 **Author:** [@vhsdream](https://github.com/vhsdream) **Created:** 11/12/2025 **Status:** ✅ Merged **Merged:** 11/12/2025 **Merged by:** [@CrazyWolf13](https://github.com/CrazyWolf13) **Base:** `main` ← **Head:** `peanut-cleaninstall` --- ### 📝 Commits (1) - [`67b52db`](https://github.com/community-scripts/ProxmoxVE/commit/67b52db36657bd1fe024072cec2eeb91ca7df5d5) PeaNUT: use clean install flag during update ### 📊 Changes **1 file changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `ct/peanut.sh` (+2 -2) </details> ### 📄 Description  ## ✍️ Description - Fixes an issue with middleware update - also removed semicolon from tags ## 🔗 Related PR / Issue When running `update` in the LXC console, I encountered this error: ``` > peanut@5.17.0 build > next build ▲ Next.js 16.0.1 (Turbopack) > Build error occurred Error: Both middleware file "./src/src/middleware.ts" and proxy file "./src/src/proxy.ts" are detected. Please use "./src/src/proxy.ts" only. Learn more: https://nextjs.org/docs/messages/middleware-to-proxy at ignore-listed frames ELIFECYCLE Command failed with exit code 1. [ERROR] in line 43: exit code 0: while executing command $STD pnpm run build:local ``` I assumed it was because something was changed upstream but the app directory wasn't cleaned during install. Adding `CLEAN_INSTALL=1` solved the issue for me. ## ✅ 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. - [ ] 🌍 **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>

kerem

2026-02-26 16:30:51 +03:00

closed this issue
added the
pull-request
label

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#7827

No description provided.

Rows
Columns