🔄 Evaluate migration from React/CoreUI to Angular/TailAdmin #115
Description
Summary
Evaluate the feasibility of migrating the frontend from the current React + CoreUI stack to Angular + TailAdmin.
Context
The current frontend is built with:
- React 18 + TypeScript
- CoreUI components
- Vite build tooling
- React Router v6
TailAdmin is an Angular admin dashboard template built on Tailwind CSS. It provides pre-built UI components, layouts, and pages with a utility-first CSS approach.
Scope of Work
This would be a major rewrite affecting:
- All frontend components (~30+ components across auth, items, reports, settings, layout, etc.)
- Routing (React Router → Angular Router)
- State management (React contexts → Angular services/RxJS)
- All frontend services (fetch-based → Angular HttpClient)
- Build tooling (Vite → Angular CLI)
- Styling approach (CoreUI/Bootstrap classes → Tailwind CSS utilities)
- Test suite (Vitest → Karma/Jest for Angular)
Evaluation Criteria
- Feature parity with current React/CoreUI implementation
- TailAdmin component coverage for existing UI needs (tables, forms, charts, modals, etc.)
- Dark mode / theming support comparison
- Bundle size and performance comparison
- Developer experience and maintainability
- Tailwind CSS utility-first approach vs CoreUI component-based approach
- Migration effort estimate
- Impact on backend (Express API should remain unchanged)
References
Notes
The Express/better-sqlite3 backend and REST API would remain unchanged — only the frontend would be affected. This is an exploratory issue to evaluate whether the migration is worthwhile. Compare alongside #114 (ngx-admin evaluation).