Summary
agent-device's bundler-agnostic core (open / snapshot / act / evidence via XCTest·ADB and the accessibility tree) works great against apps bundled with Re.Pack 5 (Rspack). But the React Native dev-loop features are coupled to Metro, so they don't apply to Re.Pack apps — a notable gap given Re.Pack is Callstack's own bundler and the backbone of Module Federation super-apps.
Context
Re.Pack 5 (Rspack) is a first-class React Native bundler and the backbone of Module Federation super-apps: a native host shell that loads JS-only mini-apps at runtime. Its dev server is react-native webpack-start, not Metro. agent-device drives such apps fine for the core loop, but the Metro-specific surface is unavailable.
What appears Metro-coupled today
metro tool / metro reload — assumes a Metro dev server; no Re.Pack/webpack-start equivalent.- Runtime/bundle hints for
open --relaunch (the metro* runtime-override flags) — geared to Metro's runtime.
- Remote dev-server workflow (
connect --remote-config, metro prepare) — Metro-shaped.
- JS debugging evidence —
react-devtools and cdp (JS heap / snapshots) route through Metro CDP / inspector; unclear if/how they resolve for a Re.Pack-served app.
Request
- Recognize and support the Re.Pack (Rspack) dev server (
webpack-start) wherever agent-device currently assumes Metro — reload, runtime hints, dev-server probing.
- Route React DevTools / JS-heap (CDP) to the RN inspector target in a bundler-agnostic way (Re.Pack apps still expose the standard RN debugging target via the app process, independent of the JS bundler).
- First-class awareness of Module Federation super-apps (host + federated mini-apps loaded at runtime) — e.g. inspecting/reloading a specific remote.
- As a minimum: document which features are Metro-only vs bundler-agnostic, so Re.Pack users know what to expect.
Environment
agent-device 0.18.1 (MCP + CLI)- React Native 0.86 (New Architecture), iOS + Android
- Re.Pack 5 (Rspack), Module Federation 2 (
@module-federation/*)
Happy to test builds against a real Re.Pack + Module Federation host/mini-app setup.
Summary
agent-device's bundler-agnostic core (open / snapshot / act / evidence via XCTest·ADB and the accessibility tree) works great against apps bundled with Re.Pack 5 (Rspack). But the React Native dev-loop features are coupled to Metro, so they don't apply to Re.Pack apps — a notable gap given Re.Pack is Callstack's own bundler and the backbone of Module Federation super-apps.Context
Re.Pack 5 (Rspack) is a first-class React Native bundler and the backbone of Module Federation super-apps: a native host shell that loads JS-only mini-apps at runtime. Its dev server is
react-native webpack-start, not Metro.agent-devicedrives such apps fine for the core loop, but the Metro-specific surface is unavailable.What appears Metro-coupled today
metrotool /metro reload— assumes a Metro dev server; no Re.Pack/webpack-startequivalent.open --relaunch(themetro*runtime-override flags) — geared to Metro's runtime.connect --remote-config,metro prepare) — Metro-shaped.react-devtoolsandcdp(JS heap / snapshots) route through Metro CDP / inspector; unclear if/how they resolve for a Re.Pack-served app.Request
webpack-start) whereveragent-devicecurrently assumes Metro — reload, runtime hints, dev-server probing.Environment
agent-device0.18.1 (MCP + CLI)@module-federation/*)Happy to test builds against a real Re.Pack + Module Federation host/mini-app setup.