-
Notifications
You must be signed in to change notification settings - Fork 1k
Open
Labels
P1sprint readyThis issue should be included in sprint planning viewsThis issue should be included in sprint planning views
Description
Summary
@a2ui/react (merged via PR #542) is not published to npm. The other renderer packages are published:
| Package | npm | Status |
|---|---|---|
@a2ui/lit |
0.8.3 | ✅ Published |
@a2ui/web_core |
0.8.0 | ✅ Published |
@a2ui/angular |
Published | ✅ Published |
@a2ui/react |
❌ 404 | Not published |
Why this matters
The React renderer exists at renderers/react/ with a package.json declaring name: "@a2ui/react" and version: "0.8.0", but it was never added to the npm publish pipeline.
This blocks downstream consumers from using the React renderer without file: dependencies, which don't work in hosted environments (Vercel, Cloudflare, etc.).
What needs to happen
- Add
renderers/reactto the existing npm publish workflow (same as@a2ui/litand@a2ui/web_core) - Run
npm publishfor@a2ui/react@0.8.0
Related
- PR Add React renderer #542 (Add React renderer — merged)
- Issue Choose and claim package names in relevant package managers #179 (Package naming — closed, but didn't include React)
- PR Pin @a2ui/web_core <0.8.4 to prevent React TextField breakage #829 (React renderer fix)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P1sprint readyThis issue should be included in sprint planning viewsThis issue should be included in sprint planning views
Type
Projects
Status
Todo