ArchitectureA supervised JVM-class runtime — OLTP on seven engines, OLAP on three. AI-native, MCP-native, observable as plain SQL.Read the architecture
Está viendo la edición Perú. Está viendo la edición Colombia. You're viewing the Pakistan edition. Cambiar a la edición global →Cambiar a la edición global →Switch to the global edition →
UIEngineering1 min read

The clients move to Vue 3 and Vuetify 4, with a Storybook over 328 components

The component library, the OS tools and the application client moved to Vue 3 and Vuetify 4. The build moved to Rolldown, the last Vue 2 dependency left, and a Storybook now covers 328 of 333 components with 752 tests.

A framework migration is not a feature, but a client left on an unsupported framework is a liability a buyer will ask about. This is the record of moving every client, and of what the migration left behind that is a feature.

The migration

  • The component library first Column filters and charts, then grid selectors, signature input, calendar, tree grid and timeline, released as a major version with the breaking grid properties named.
  • The OS tools in place The Vue 2 application was replaced in one commit of 1,261 files and 285,000 deleted lines; four tools moved in a day, the desktop six days later.
  • The toolchain Vite 6, TypeScript 5.8, Vuetify 4, and the bundler moved to Rolldown. The last Vue 2 dependency left with the API viewer, so the audit reports no vulnerabilities.

What it left behind

  • A Storybook 328 of 333 OS components, 157 story files, 752 tests, with the product defects the stories surfaced recorded in the plan. The application client's Storybook carries skin toggles for two design systems.
  • A regression found and fixed Virtual scroll and tree rendering slowed after the move and were rebuilt without a JSON conversion.

The number that matters to a buyer is the vulnerability count on the client, and it is zero.

On the platformUI ExperiencePlatform

All posts