ui-router-server / ui-router-server / MountConfig

Interface: MountConfig

Defined in: index.ts:34

Properties

Property	Type	Description	Defined in
config?	UrlMatcherCompilerConfig	Matcher compiler options for 'matcher' mounts (defaults: strict, case-sensitive).	index.ts:50
otherwise?	{ state: string; }	Projection of the client's otherwise() rule. state references a declared, url-less state (url-less so the unmatched url stays in the address bar, like a server 404 — mirroring the real rule's semantics). When declared, unknown paths under this mount verdict as shell with status 404: the resource genuinely doesn't exist and the shell IS the error page (never 200) — the client boots at the retained path and its own otherwise rule renders the rich notFound state. Redirect rules and route matches take precedence; undeclared keeps the notFound verdict.	index.ts:61
otherwise.state	string	-	index.ts:61
redirects?	RedirectRule[]	when()-style pattern rules, evaluated before per-state redirectTo entries.	index.ts:38
routes	RouteDeclaration[]	The mount's state tree; dotted names nest, urls append (see RouteDeclaration).	index.ts:36
strategy?	"matcher" | "simulate"	'matcher' (default): dependency-free pattern matching plus data redirects. 'simulate': replay through a headless @uirouter/core router — the tier where routing that data cannot express (hooks, resolves, redirectTo functions) will live. Those are NOT yet reachable through MountConfig: both strategies consume the same RouteDeclaration data subset today, deliberately, so strategy stays a pure cost knob; the config widens later (e.g. an auth tier).	index.ts:48