Ux Router Laravel Package

Product Decisions This Supports

• Feature: server-driven routing in the frontend. Symfony UX Router exposes backend routes to JavaScript, so teams can generate URLs client-side instead of hardcoding paths. This directly supports any roadmap item involving SPA-like navigation, Inertia/React/Vue frontends, or progressive enhancement where route parity matters.
• Build vs. buy: This is the "buy" (adopt) answer for route bridging. Laravel teams currently reach for Ziggy; PHP/Symfony teams now have a first-party equivalent. Choosing this avoids maintaining a bespoke route-dump script and the drift bugs that come with it.
• Roadmap sequencing: v3.6.0 marks the package's initial introduction plus two stabilizing features (default-locale fallback, route dumping when no dump directory exists). Treat it as newly available but early; schedule adoption behind a spike rather than as a hard dependency of a launch-critical milestone.
• i18n/localization decisions: The locale fallback (#4076) means localized route generation degrades gracefully to the app default locale instead of failing. This unlocks shipping localized URLs without a full translation matrix on day one.
• Deployment/CI decisions: The route-dump fix (#4082) removes a class of build-environment failures (containers built without a dump directory). Relevant if you deploy via containers or build artifacts.
• Use cases it unblocks: localized marketing URLs, client-side redirects after form posts, generating links in JS-driven modals/wizards, cache-safe URL generation in edge/CDN-rendered components.

When to Consider This Package

Consider adoption when:

• Your frontend needs to construct URLs that the backend owns (named routes, parameterized paths), and hardcoded strings are already causing 404s or broken links after refactors.
• You are on the Symfony/PHP stack and want a first-party route bridge rather than a community shim (Laravel equivalents: Ziggy). Note the ecosystem mismatch — if the product is Laravel-first, verify fit before committing; the concept transfers, the package may not.
• You ship a multi-locale product and want route generation to fall back to the default locale rather than throw.
• Your deployment uses container builds where a route dump directory may not exist — the #4082 fix is specifically for you.
• You want reduced frontend/backend coupling: route changes become a backend concern only.

Look elsewhere or wait when:

• The app is server-rendered with no meaningful JS route generation — the value is near zero.
• You need long-term API stability guarantees: this is the initial introduction (feature #1234) plus a minor tooling bump; treat maturity as unproven until a few more patch releases land.
• Your frontend is fully decoupled (separate repo/app) and consumes a documented public API — a router dump tied to the backend app is the wrong abstraction.
• You already have a maintained internal solution; the migration cost likely exceeds the benefit at this stage.

How to Pitch It (Stakeholders)

For executives: This release makes a first-party capability available that removes a recurring source of broken links and duplicated routing logic between backend and frontend. The business value is fewer production defects from URL drift and less engineering time spent maintaining custom glue code. It is early-stage — recommend a contained pilot, not a platform-wide commitment.

For engineering: v3.6.0 introduces the UX Router package, with two immediately useful behaviors: route dumping now works when the container is built without a dump directory (removes a known CI/container failure mode), and route generation falls back to the application default locale (makes localized URLs safe by default). Remaining changes are tooling dependency updates. Risk is low but maturity is unproven — scope a spike, confirm behavior in your build pipeline, and gate wider rollout on a clean pilot.