Skip to content

docs: no-build modulepreload section describes pre-#161 behavior #168

Description

@vivek7405

Problem

The docs site no-build page ("Module graph and modulepreload hints" section, docs/app/docs/no-build/page.ts) described modulepreload hints as covering "components plus their transitive dependencies" and only excluded .server.* files themselves. Read precisely, that matched the PRE-#161 behavior: a plain util imported THROUGH a server action (a transitive dep that is not itself a .server.* file) would be preloaded and then 404.

PR #161 made the preload walk stop at the .server.* boundary (like the authorization gate), so those transitive server-only deps are excluded too. The doc paragraph needed to say so: the preload set is exactly the set the page actually fetches.

This was a doc-sync follow-up that #161 itself should have carried; it was marked N/A for user-facing docs at the time, which was wrong on re-audit.

Acceptance criteria

  • The no-build modulepreload paragraph states the walk stops at the .server.* boundary (transitive server-only deps excluded)
  • Docs app boots and /docs/no-build renders 200 with the corrected text

Resolved by #165 (merged). Filed retroactively so the work is tracked on the board per the project convention.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions