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
Commit 3a7ff44
Browse filesBrowse the repository at this point in the historyBrowse files
fix: full-reload on document shell and server-only module edits (solidjs/solid#3151)
The document shell hydrates the whole document, so no refresh-boundary
component swap can ever apply an edit to it — updates were accepted and
silently absorbed. The client compile of the resolved start.document /
src/Document.* module now declines HMR (self-accept + invalidate), so a
save full-reloads the page.
Separately, server-environment hot updates for files with no modules in
the client graph (client-mode documents, authored entry-server,
middleware) now send a browser full-reload instead of being suppressed:
the suppression protects client HMR from full-reload races, but a
server-only file has no client update to race with — staying silent just
leaves the browser rendering stale server output.
Co-authored-by: Cursor <cursoragent@cursor.com>
Document shell edits now trigger a full page reload instead of being silently absorbed (solidjs/solid#3151). Two sides: the resolved `start.document` / `src/Document.*` module declines HMR in its client compile (it hydrates the whole `document`, so no component swap can ever apply — self-accept + invalidate makes Vite reload instead), and server-environment updates for files with no client-graph counterpart (client-mode documents, authored entry-server, middleware) send a browser full-reload rather than staying suppressed — the suppression exists to protect client HMR from full-reload races, but a server-only file has no client update to race with.
0 commit comments