CMS Route Configuration in @decocms/tanstack

Reusable route configuration factories that live in @decocms/tanstack. Sites use thin wrappers that delegate to these factories, keeping route files small and consistent across all Deco sites.

Import split (two packages, different export-map shapes):

• Runtime functions and components — cmsRouteConfig, cmsHomeRouteConfig, decoMetaRouteConfig, decoRenderRouteConfig, decoInvokeRouteConfig (admin-route factories, 7.10.0+; the former decoMetaRoute/decoRenderRoute/decoInvokeRoute literal exports were removed — see the footgun note below), loadCmsPage, loadCmsHomePage, loadDeferredSection, DecoPageRenderer, CmsPage, NotFoundPage — import from @decocms/tanstack (package root only; packages/tanstack/package.json's exports map has just ., ./vite, ./daemon — there is no ./routes, ./hooks, or ./cms subpath).
• Types and SEO/section primitives — ResolvedSection, DeferredSection, PageSeo, registerSeoSections, extractSeoFromProps, extractSeoFromSections, resolvePageSeoBlock — import from @decocms/blocks/cms, a separate package.

When to Use This Skill

• Setting up routes for a new Deco TanStack storefront
• Migrating Fresh routes to TanStack Start
• Debugging why variant changes trigger server re-fetches
• Configuring cache headers per page type
• Setting up admin protocol routes (meta, render, invoke)
• Understanding the relationship between loaderDeps, staleTime, and server-side caching