e79bffc1f1
Panel functional but yarn build:production fails with 16 webpack errors. css-loader conflict between Blueprint beta-2026-01 and Pterodactyl v1.12.1. PteroStats needs reinstall when resolved. Chronicler #29
Task: Pterodactyl Blueprint Asset Build Issue
Status: ⚠️ KNOWN ISSUE — monitoring for Blueprint fix Discovered: March 13, 2026 (Chronicler #29) Priority: LOW — panel is fully functional
Summary
After updating Pterodactyl Panel v1.12.0 → v1.12.1, Blueprint extensions (modpackinstaller, subdomains) were reinstalled successfully but webpack asset rebuild fails with 16 errors.
Root Cause
Blueprint beta-2026-01 has a css-loader version conflict with Pterodactyl v1.12.1 node dependencies. Extensions built for Blueprint beta-2025-04.
Key errors:
- options.modules.exportLocalsConvention validation failure in css-loader
- xterm-addon-unicode11 module not found
Current State
- Panel fully functional (serving cached pre-update assets)
- All servers manageable via panel
- Wings unaffected on TX1 and NC1
- Blueprint extensions registered: modpackinstaller, subdomains
- yarn build:production fails with 16 webpack errors
- PteroStats wiped by update — needs reinstall from BuiltByBit
Resolution Path
- Wait for Blueprint beta-2026-02+ with css-loader fix
- OR manually patch node_modules css-loader exportLocalsConvention
- After build works, reinstall PteroStats (paid BuiltByBit resource)
Do NOT
- Do not run yarn build:production until Blueprint is updated
- Do not run blueprint -install on new extensions until fixed
- Panel works fine as-is