Skip to content

fix: settle an in-place dev reload in 300ms instead of 2s - #1586

Merged
vivek7405 merged 1 commit into
mainfrom
fix/relay-in-process-quiet
Oct 7, 2026
Merged

vivek7405 merged 1 commit into
mainfrom
fix/relay-in-process-quiet

Conversation

@vivek7405

Copy link
Copy Markdown
Collaborator

Follow-up to #1584 (refs #1575). A server that applies edits in place (Bun's one long-lived dev server, --no-hot) marks its reload frames inPlace; the relay settles a batch of only those after 300ms instead of 2000ms. A batch with any restart signal keeps 2000ms; the 5s cap is unchanged. Tests: relay browser suite (Chromium/Firefox/WebKit), SseHub unit, bun test/bun/dev-morph-verdict.mjs, bun test/bun/dev-reload-stress.mjs.

https://claude.ai/code/session_01SZ72LSPAo4NvYvBDSD6RLo

The browser relay held every reload for a 2s quiet window so a burst
would not reload into a Node server about to be restarted. Bun's dev
server now applies edits in place, so that wait was most of the
save-to-paint time (3.8s measured in a hosted preview). Frames from a
server that reloads in place say so, and a batch made only of those
settles after 300ms; any restart signal keeps the 2s window and the 5s
cap is unchanged.

Refs #1575

Claude-Session: https://claude.ai/code/session_01SZ72LSPAo4NvYvBDSD6RLo
@pilots-run

pilots-run Bot commented Oct 7, 2026

Copy link
Copy Markdown

Preview for 52873ba was not built: compose file has unsupported keys

Next: fix the listed keys in the compose file

@vivek7405
vivek7405 merged commit 053f0ac into main Oct 7, 2026
9 of 11 checks passed
@vivek7405
vivek7405 deleted the fix/relay-in-process-quiet branch October 7, 2026 12:25
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