Release Notes
Recent versions introduced portable miniapp navigation, manifest-backed param contracts, React Navigation default header behavior changes, and built-in miniapp router hooks in runtime deps.
Recent Versions (0.6.4 → 0.5.19)
0.6.4
- Added built-in miniapp hook runtime deps:
useMiniappRoute,useMiniappRouter, anduseMiniappTabsare now available by default alongsideuseNamedPersistentState.
0.6.3
- Fixed hook dependency safety and persistent-state re-initialization across miniapp namespace changes (no public API changes).
0.6.2
- React Navigation engine stack headers are now hidden by default unless explicitly configured in manifest options.
0.6.1
- Added manifest-declared page param contracts via
paramsSchemaandinitialParams. - Navigation actions now validate merged params before mutating state, so invalid params fail fast.
0.6.0
- Added portable navigation manifests with stacks, tabs, cards, modals, and fullscreen modals.
- Added router hooks and host adapters for React Navigation and Expo Router.
- Added local manifest/local component support and multi-page cache metadata.
0.5.19
- Updated Jest configuration (internal tooling update).
Compatibility
Legacy miniapps still load
Older miniapps that only mark one component with
root: true continue to work. The runtime and dashboard now normalize them into a one-screen manifest-backed bundle.What Changed In Practice
JSON
{
"components": [
{
"key": "support/HomePage",
"name": "HomePage",
"value": "compiled screen code"
}
],
"navigation": {
"version": 1,
"rootId": "root-stack",
"nodes": []
}
}If the server omits navigation, dpage synthesizes a one-screen stack manifest automatically. If the server includes it, the runtime preserves the multi-page route graph and can render it with the portable renderer or React Navigation.