Skip to content

docs: sync the modulepreload section with the #161 server-boundary fix#165

Merged
vivek7405 merged 1 commit into
mainfrom
docs/preload-server-boundary-sync
May 31, 2026
Merged

docs: sync the modulepreload section with the #161 server-boundary fix#165
vivek7405 merged 1 commit into
mainfrom
docs/preload-server-boundary-sync

Conversation

@vivek7405

Copy link
Copy Markdown
Collaborator

Summary

Follow-up doc sync for #161. The no-build page's "Module graph and modulepreload hints" section described preloads as "components plus their transitive dependencies" and only excluded .server.* files themselves. Read precisely, that matched the pre-#161 behavior, where a plain util imported through a server action (a transitive dep that is not itself a .server.* file) would be preloaded and then 404.

#161 made the preload walk stop at the .server.* boundary, exactly like the authorization gate, so those transitive server-only deps are excluded too. This updates the one paragraph to say so: the preload set is exactly the set the page actually fetches.

No code change. The docs app boots and /docs/no-build renders 200 with the new clause.

The no-build page's modulepreload section said preloads cover "transitive
dependencies" and only carved out .server.* files themselves, which read
as the pre-#161 behavior (a plain util imported through a server action
would be preloaded). #161 made the walk stop at the .server boundary, so
those transitive server-only deps are excluded too. Document that the
preload set is exactly the set the page fetches.
@vivek7405 vivek7405 self-assigned this May 31, 2026
@vivek7405 vivek7405 merged commit 45d19f5 into main May 31, 2026
5 checks passed
@vivek7405 vivek7405 deleted the docs/preload-server-boundary-sync branch May 31, 2026 21:56
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