Beta Testers Wanted: v1.0.0 - Major UI/UX Overhaul and Performance

[MickLesk]

🧪 We need your help testing v1.0.0-pre1!

v1.0.0 is the biggest update to ProxmoxVE-Local yet — complete UI/UX overhaul, massive performance improvements, and many new features. Before we release it as stable, we need community testers to help catch bugs and give feedback.

---

What's new in v1.0.0-pre1?

• ⚡ Performance: Page loads in <1s (was 14-25s), cached PB queries <200ms
• 🎨 UI Overhaul: Compact navbar, rewritten modals, new filter bar, dark mode fixes
• 📝 Script Notes: Per-script notes with sharing support
• ⚙️ Server Presets: Save/load server configurations per PVE host
• 🔄 Sync Modal: Real-time progress with retry capability
• 📊 Generator Tab: Full script generator for custom LXC/VM provisioning
• 🟢 Server Status: Live indicator showing PVE host reachability
• 🔖 Version Display: Auto-update detection with release notes

Full changelog: v1.0.0-pre1 Release Notes
Related PR: #545

---

How to install the pre-release

Requirements: Existing ProxmoxVE-Local installation (v0.5.8 or any prior version)

curl -fsSL https://github.com/community-scripts/ProxmoxVE-Local/releases/download/v1.0.0-pre1/pre-release-updater.sh \
  -o /opt/pve-local-prerelease-updater.sh && \
  chmod +x /opt/pve-local-prerelease-updater.sh && \
  bash /opt/pve-local-prerelease-updater.sh

systemctl restart pvescriptslocal

The updater script will:

1. Show all available pre-releases (newest first)
2. Let you pick which one to install via numbered menu
3. Automatically backup your data, .env, and database
4. Download, install, migrate, and build

💡 Rollback: If something breaks, the script creates a timestamped backup in /tmp/pve-prerelease-backup-*. Restore from there and restart the service.

---

What we need from testers

Please report any issues you find as a comment on this issue with:

1. What happened (screenshot if possible)
2. What you expected
3. Your environment (Proxmox version, browser, Node.js version)
4. Steps to reproduce

Known areas to test:

• Fresh install from v0.5.8 → pre1 upgrade path
• Generator tab functionality
• Script notes (create, edit, delete)
• Server presets (save, load, delete)
• Server status indicator accuracy
• Sync modal (full resync)
• Filter bar (category, search, sort, badges)
• Dark mode appearance
• Modal navigation (arrow keys, escape)
• Performance (page load times, tab switching)

---

⚠️ Important

• This is a pre-release — do not use in production environments
• Your data is backed up automatically before the update
• Future pre-releases (pre2, pre3, ...) will appear in the updater script automatically
• Once stable, the final v1.0.0 will be released on main

Thank you for helping make v1.0.0 the best release yet! 🙏

[MickLesk]

Known issues:

• Generator sometimes stupid while downloading not downloaded scripts
• some Terminal Bugs with direct install from Generator
• Expose LXC sometimes not work
• Icons from VED Scripts sometimes "empty" and sometimes filled.

[snakefood3232]

I can help fix any bugs found during the v1.0.0-pre1 beta test. I'd handle UI/UX issues or performance regressions by directly patching the React/Next.js components and optimizing the cached queries. I can have a PR ready within a day, as I regularly work with full-stack TypeScript in production environments.

[snakefood3232]

The performance improvements from 14-25s to <1s page loads are a major win. I can help fix any bugs that surface from the UI overhaul or new features like server presets. I'd handle this by reviewing the related PR #545 and writing targeted tests for the sync modal and generator tab. I can have a PR up in a day, as I regularly work with full-stack TypeScript/React/Next.js in production.

[Thundernerd]

I believe the msg (ln 41) function's output is being picked up by other things causing jq to fail to read the output from fetch_prereleases (ln 339) because it contains Fetching available pre-releases from GitHub... (ln 82)

[MickLesk]

I believe the msg (ln 41) function's output is being picked up by other things causing jq to fail to read the output from fetch_prereleases (ln 339) because it contains Fetching available pre-releases from GitHub... (ln 82)

fixed, can you try again?

[Thundernerd]

I believe the msg (ln 41) function's output is being picked up by other things causing jq to fail to read the output from fetch_prereleases (ln 339) because it contains Fetching available pre-releases from GitHub... (ln 82)

fixed, can you try again?

It seemed to pass the earlier issues but now this has happened

You are about to update:
  From: v0.5.8
  To:   v1.0.0-pre1

Continue? [y/N]: y
[INFO] Backing up current installation...
[OK] Backup created at: /tmp/pve-prerelease-backup-20260420-155459
[INFO] Installing pre-release: v1.0.0-pre1...
[INFO] Downloading v1.0.0-pre1...
[OK] Downloaded (1.5M)
[INFO] Extracting...
[INFO] Installing files to /opt/pve-scripts-local...
[OK] Files installed
[INFO] Installing npm dependencies...
[WARN] npm ci failed, trying npm install...

> pve-scripts-local@0.5.8 postinstall
> prisma generate

sh: 1: prisma: not found
npm error code 127
npm error path /opt/pve-scripts-local
npm error command failed
npm error command sh -c prisma generate

[MickLesk]

work fine atm for me;

try again with:

curl -fsSL https://github.com/community-scripts/ProxmoxVE-Local/releases/download/v1.0.0-pre1/pre-release-updater.sh \
  -o /opt/pve-local-prerelease-updater.sh && \
  chmod +x /opt/pve-local-prerelease-updater.sh && \
  bash /opt/pve-local-prerelease-updater.sh

[Thundernerd]

Did you change something to it? That was what I already used but it seems to work now... 😅

[Thundernerd]

Seems like I cheered too soon. I'm running it with npm start and get this output

root@pve-scripts-local:/opt/pve-scripts-local# npm start

> pve-scripts-local@0.5.8 start
> node --import tsx server.js

node:internal/modules/package_json_reader:301
  throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
        ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'tsx' imported from /opt/pve-scripts-local/
    at Object.getPackageJSONURL (node:internal/modules/package_json_reader:301:9)
    at packageResolve (node:internal/modules/esm/resolve:768:81)
    at moduleResolve (node:internal/modules/esm/resolve:859:18)
    at defaultResolve (node:internal/modules/esm/resolve:991:11)
    at #cachedDefaultResolve (node:internal/modules/esm/loader:719:20)
    at #resolveAndMaybeBlockOnLoaderThread (node:internal/modules/esm/loader:736:38)
    at ModuleLoader.resolveSync (node:internal/modules/esm/loader:765:52)
    at #resolve (node:internal/modules/esm/loader:701:17)
    at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:621:35)
    at onImport.tracePromise.__proto__ (node:internal/modules/esm/loader:650:32) {
  code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v24.14.1```

[MickLesk]

Why npm start? it should overwrite your old Install with the new and this Run with systemd

[Thundernerd]

I used npm start because it did not overwrite the existing installation but went into a different folder.

[MickLesk]

Then its Not possible. Its an running Migration inside. Then deploy the current Version with Our Helper Script and Run Script. Or duplicate your exist LXC

[Thundernerd]

Some extra info: the existing folder name is ProxmoxVE-Local and the new one is pve-scripts-local.

You might want to check if this is intended.