Skip to content
MigrationVersion 6.0.2

Moving from v5 to v6 ​

Ray Template 6.0.0 starts a new major release line. v6 reorganizes the admin application, documentation site, and shared packages into a monorepo. In-place upgrades from v5 are unsupported. Review internal import paths, APIs, deployment settings, and browser data before migrating. Existing v5 projects can stay on v5.

VersionWhere to start
v6.0.0Start new projects from the v6 workspace. See Quick start and v6 Monorepo Architecture.
v5legacy/v5 preserves the complete source before the split. The branch points to 6f095b7 with manifest version 5.2.5. For a tagged snapshot, use v5.2.4.

What changed in v6 ​

Areav6 entry points and conventions
Application structureThe former root src/, mock/, public/, app environment files, and index.html moved under apps/admin/. Review environment variables, container configuration, and build scripts against the v6 entry points.
Components and utilitiesImport shared code through each package's public entry points, such as @ray-template/ui/table-pro, @ray-template/composables/useDevice, and @ray-template/utils/precision. Within Ray Admin, @/ resolves to the application's own src/.
Component integrationIn v6, RTablePro accepts either data or request(params, signal). useTablePro retains [register, actions] and onRegister. Use the current API for requests and instance methods.
Routing, permissions, and requestsShared packages provide route validation, the HTTP client, and the layout. Ray Admin supplies the view registry, session handling, access checks, request headers, themes, and language.
Docs and demoThe VitePress site in apps/docs/ runs examples through public package exports. The hosted admin is at /ray-template/ and the docs are at /ray-template/docs/, with English at /ray-template/docs/en/.

Adopt v6 in an existing project ​

  1. Start from a new workspace or branch. Keep a way to roll back to your v5 code and deployment. Configure dependencies, environment variables, API endpoints, and CI for v6.
  2. Move pages, endpoints, and menus one feature at a time. Review old deep imports, route JSON, and custom interceptors against the page example, routing conventions, and TablePro API.
  3. Verify v6 with a separate browser profile or deployment origin. localStorage is scoped to the origin, so different paths on the same host share session and preference storage. Existing settings, lock state, cache, and sign-in state require project-specific migration.
  4. Check sign-in, permissions, direct navigation, APIs, caching, and deployment paths before switching traffic. Run pnpm harness verify. Use pnpm pages:build for a combined deployment. Checks and deployment