menu-auth-routes

To generate TanStack Router authentication routes from a MenuItem tree, define your MenuItem array and trigger the generation process. This automatically creates route files under src/routes/_authentication and overwrites existing scaffold pages.

Keeping bilingual menu i18n entries in sync involves using staticData.key as the route key to update src/locales/business/Menu/en.yaml and zh.yaml files. This ensures route and internationalization data update together when menus change.

Yes, this route generation approach overwrites existing scaffold pages with the same name. It enforces kebab-case file structures for route URLs and generates corresponding pages for leaf nodes to achieve rapid deployment.

Yes, you can bulk deploy routes and i18n from API responses or configuration data. The tool processes the provided MenuItem tree to simultaneously generate authentication routes and bilingual Menu entries.

You need to generate menu-driven routes for TanStack Router when admin menus change, when adding new backend pages, or when bulk deploying routing structures and internationalization data from external configuration sources.

Generated route URLs might not match if staticData.key is not properly defined. The generation process strictly enforces staticData.key as the route key and maintains consistency between route URLs and kebab-case file structures.