# Vuexy Components — DEPRECATED

> This document is deprecated. The Crewli SPA is migrating from Vuetify
> to PrimeVue per [RFC-WS-FRONTEND-PRIMEVUE](./RFC-WS-FRONTEND-PRIMEVUE.md).

## During F4 component migration

The SPA contains both Vuetify and PrimeVue components simultaneously.
Reference the active framework per surface:

- **For PrimeVue conventions** (target state): see [`PRIMEVUE_COMPONENTS.md`](./PRIMEVUE_COMPONENTS.md)
- **For Vuetify conventions on un-migrated surfaces**: see git history
  at commit `1c449ff6204cae6371da08c34ea8934d6b2ffcb8` (HEAD of `main`
  immediately before F2):

  ```bash
  git show 1c449ff6204cae6371da08c34ea8934d6b2ffcb8:dev-docs/VUEXY_COMPONENTS.md
  ```

## End of life

This file is deleted entirely in F6 cleanup once F4a–F4d have migrated
all surfaces to PrimeVue and F5 has validated the migration.

## Why a stub instead of immediate deletion

Per project decision 2026-05-10: during F4a–F4c, some F4 developers
will need to look up Vuetify conventions for components on un-migrated
surfaces. Git-history archaeology
(`git show 1c449ff6204cae6371da08c34ea8934d6b2ffcb8:dev-docs/VUEXY_COMPONENTS.md`)
is workable but inconvenient. This stub provides an explicit forwarding
marker, with the actual content recoverable via git history per the
explicit SHA above.