bridge: Request — badge build blocked, need decision (skip or patch webpack)
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
ab0b328bd2
commit
0d6752792a
@@ -0,0 +1,25 @@
|
||||
# Architectural Request
|
||||
|
||||
**Date:** 2026-04-12
|
||||
**Topic:** Dashboard badges blocked by Blueprint CSS module build errors — decision needed
|
||||
|
||||
## 1. Current State
|
||||
Badge injection into ServerRow.tsx is correct. But `yarn build:production` fails on 7 pre-existing CSS module errors from Blueprint beta — not caused by our code.
|
||||
|
||||
## 2. The Blocker
|
||||
Blueprint beta-2026-01's webpack config doesn't have a CSS module loader configured. This breaks `yarn build:production` for any panel with Blueprint installed. Our badge code can't compile.
|
||||
|
||||
## 3. Decision for Michael
|
||||
|
||||
**Option A: Skip badges for v1.0.0 launch** (recommended)
|
||||
- Admin page + console widget both work
|
||||
- Badges are nice-to-have, not core functionality
|
||||
- Add badges in v1.1.0 when Blueprint fixes their build or we find a workaround
|
||||
- Zero risk to launch timeline
|
||||
|
||||
**Option B: Patch webpack config**
|
||||
- Add `css-loader` with modules support to Blueprint's webpack
|
||||
- Risk: could break other Blueprint components, and gets overwritten on Blueprint updates
|
||||
- Not recommended 52 hours before launch
|
||||
|
||||
Which way do you want to go?
|
||||
Reference in New Issue
Block a user