Error Reference
Exact Cookbook Router error messages, why they occur, and how to remove the cause rather than the evidence.
Use the exact message
Errors are contracts. Search the text you received, including the route ID or field when useful. Each entry explains the symptom, the source condition, and the repair.
Route definitions
Shape, IDs, paths, redirects, metadata, and route-local fields.
Route-tree composition
Parents, cycles, absolute children, and modular declarations.
Path and URL state
Constraints, descriptors, hashes, and unsupported matching options.
Navigation and middleware
Href generation, redirects, disposal, and internal navigation.
React, slots, and intercepts
Provider context, slot declarations, intercept targets, and fallbacks.
CLI and plugins
Configuration, extraction, output safety, and build adapters.
Dynamic values
The catalog uses ... where the runtime message inserts a route ID, path, parameter, slot, export, or target. Do not remove that context when reporting a bug. It is usually the shortest path back to the bad declaration.
CLI contract types
Public CLI data contracts for filesystems, route inputs, config loading, command results, manifests, watch handles, and build integration.
Route-definition validation errors
Exact validation failures for route arrays, route objects, IDs, paths, redirects, metadata, and route-local fields.