You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
feat: show the build and reload status of jaspr serve on the page #1004
During jaspr serve the page gives no hint whether it shows the current code. I'd like a small status indicator on the page in dev mode that shows what the CLI already knows:
Building: a build is running.
Build failed: the last build has errors, the page shows the state before it.
Updating: the build is done, the reload hasn't been applied in this tab yet.
Up to date: the tab shows the last successful build.
This is independent of how the update is applied. It should work the same with --auto reload, --auto restart and --auto refresh. Without --auto, it would show that a newer build is available until I press r in the terminal.
Why I'm asking: I usually keep the browser behind the editor and only look at the terminal now and then. Twice in the last weeks I looked at stale content without noticing:
After a failed build, the page keeps the last good state. Unless I check the terminal, a typo looks like "my change has no effect".
The interesting case is switching back to a tab: on visibilitychange the indicator could show "Updating" until the CLI confirms the build this tab is on, and then switch to "Up to date".
Additional Context
This could be a first, small piece of the toolbar from #788, or live in it later. It doesn't need the component tree or any inspection, only the build results and the reload state per client, which jaspr serve has already.
A few things I'd leave to you:
On by default in dev mode or behind a flag (e.g. jaspr serve --status).
Where it sits and how it looks. It must not affect layout or hydration, and it must never be part of a release build.
Whether the state is pushed through the existing debug service extensions (like ext.jaspr.reload_stylesheets) or another channel.
Activity
schultek commentedon Nov 18, 2026
I like this idea. I already started with #788 locally so I'll include it in the work there.