Skip to content

Mount AppNav standalone too, on @clawnify/app 0.4.8 - #13

Merged
pallaoro merged 1 commit into
mainfrom
app-sdk-0.4.8
Nov 17, 2026
Merged

pallaoro merged 1 commit into
mainfrom
app-sdk-0.4.8

Conversation

@pallaoro

Copy link
Copy Markdown
Member

used to mount only inside the dashboard. It now mounts in both modes: inside the dashboard it still hands HOST_NAV to the host; elsewhere the header stays the navigation and the standalone renderer draws only the SDK's notice card (nav.card) below the page. On 0.4.8 a mounted AppNav also shows the SDK's dialog on a self-hosted copy.

@clawnify/db moves to ^0.4.3, the version @clawnify/app 0.4.8 depends on, so a single copy is installed (two copies leave the app's DB uninitialised).

Checks run before and after the change: Build, node tests (70/70 before and after), tsc --noEmit via typescript 5.9 (8 errors before and after, same files; typescript is not a dependency here). Lockfile has no file: or tarball paths.

<AppNav> used to mount only inside the dashboard. It now mounts in both modes: inside the dashboard it still hands HOST_NAV to the host; elsewhere the header stays the navigation and the standalone renderer draws only the SDK's notice card (nav.card) below the page. On 0.4.8 a mounted AppNav also shows the SDK's dialog on a self-hosted copy.

@clawnify/db moves to ^0.4.3, the version @clawnify/app 0.4.8 depends on, so a single copy is installed (two copies leave the app's DB uninitialised).
@pallaoro
pallaoro merged commit f7d1660 into main Nov 17, 2026
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