Skip to content

armgit / spree

Public Imported from GitHub
0

Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.

Record build-time typed route composition as a 5.6 plan open question

Damian Legawiecc91ec2be8532
diff --git a/docs/plans/5.6-project-layout-and-dashboard.md b/docs/plans/5.6-project-layout-and-dashboard.md
index 29f602d61f..7522c8a81f 100644
--- a/docs/plans/5.6-project-layout-and-dashboard.md
+++ b/docs/plans/5.6-project-layout-and-dashboard.md
@@ -552,6 +552,8 @@ Manual QA checklist:
4. **When exactly does `backend/` support get dropped?** The plan says "by 6.0 GA". Open: do we want a 5.7 deprecation warning step in between, or jump straight from "silent dual-support in 5.6" to "warning in 6.0 RC" to "removed in 6.0 GA"? The 5.6/6.0 cycle is short enough that one warning step at 6.0 RC is probably enough.
+5. **Build-time typed route composition (future).** Plugin routes currently go through the runtime route registry + catch-all dispatcher — simple, works for in-app customization, but plugin-route `<Link>`s need `as never` casts and get no route-level code splitting. Since the shell is source-only and the Vite plugin already knows the discovered plugin list at build time, a later phase could additionally compile statically-declared plugin routes into the host's route tree (typed links, per-route chunks) while keeping the runtime registry for dynamic cases. Requires route declarations to be importable without executing the full plugin module — likely a conventional `dashboard/routes` entry. Not preview-blocking; design when the first big plugin needs it.
+
## References
- **Supersedes (partial):** `docs/plans/5.4-spree-starter-and-create-spree-app.md` — specifically the `apps/admin/` reference (now `apps/dashboard/`) and the `backend/` directory name (now `api/` in 5.6+ generated projects).