feat(routing): index React Router framework pages - #3
Open
bompus wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
React Router framework-mode apps declare pages in
app/routes.ts; those declarations previously produced no routes or page links. Literal exported route trees now produce pages fromroute,index,layout, andprefix, resolve their exact default component modules, and participate in existing navigation matching. Nested index pages take precedence over their parent layouts.Module links refresh after sync, including a missing default export being added or changed. Main-thread and resolver-worker parsing load the required grammars. The reader deliberately excludes computed configuration, custom app directories,
relative, anonymous defaults, and re-exports.Validation: the pinned official route tree yields all seven expected page/module pairs; focused coverage includes navigation, config/module edits, false-export strings, nested indexes, and a fresh compiled process with parse/resolver workers. Build passed; 112 focused/control tests passed with WASM; full native suite passed (4,353 tests, 46 skipped). Independent review findings were fixed and rechecked.
This is step 1 of the approved application-router plan, stacked on #2. Its base keeps the preceding HTTP/Nuxt changes out of this diff.