Skip to content

feat: add CLI dynamic widget generation#207

Open
V3RON wants to merge 5 commits into
mainfrom
feat/voltra-cli-dynamic-widgets
Open

feat: add CLI dynamic widget generation#207
V3RON wants to merge 5 commits into
mainfrom
feat/voltra-cli-dynamic-widgets

Conversation

@V3RON

@V3RON V3RON commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

What is this?

This PR brings Dynamic Widget generation to the Voltra CLI so React Native CLI projects can use the same widget workflow that Expo projects already have. voltra apply now understands widget entry declarations and generates the native and Metro-facing pieces required for on-device widget rendering.

How does it work?

The CLI keeps widget entries project-relative, validates that Dynamic Widget modules default-export a render function, and writes platform manifests under .voltra. It also generates dynamic placeholder initial states, iOS client widget provider scaffolding with AppIntent support, Android client widget receivers and configuration defaults, and release build hooks that bake widget bundles through @use-voltra/metro. Generated Android Gradle and iOS Xcode wiring is idempotent and cleaned up when dynamic widgets are removed.

Why is this useful?

React Native CLI users no longer need the Expo config-plugin path to ship Dynamic Widgets. The same config-level widget model now works through voltra apply, making the experimental dynamic widget workflow available across both supported setup flows while preserving existing server-rendered widget behavior.

V3RON added 5 commits June 25, 2026 09:35
Port dynamic widget manifest, placeholder, native wiring, and release bundling generation to voltra apply for React Native CLI projects.
Apply repository formatter output after adding CLI dynamic widget generation.
Use the app's own Metro instance when loading Metro APIs and add a regression test.
Use an error-only reporter for the widget Metro config so startup banners and info logs stay quiet while real Metro failures still surface.
Drop custom logging for Metro events that the upstream terminal reporter does not render, and keep the reporter limited to terminal-visible error paths.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant