- Install Vite, React Router, and React Helmet Async
- Create Vite configuration with base path support
- Create router configuration mapping all existing routes
- Update entry point from _app.tsx to main.tsx with RouterProvider
- Replace Next.js components:
  - Link -> react-router-dom Link
  - useRouter -> useNavigate/useLocation
  - Image -> native img tags
  - Head -> react-helmet-async Helmet
  - dynamic -> React.lazy with Suspense
- Update all component imports and navigation
- Update Layout component to use Outlet for nested routes
- Fix bowser import to use default export
- Update Dockerfile to use dist/ instead of out/
- Update turbo.json build outputs
- Remove Next.js dependencies and config files
- Update package.json scripts for Vite
- Retain BASE_PATH feature with __PATH_PREFIX__ placeholder

Co-authored-by: benscobie <[email protected]>

- Replace Next.js ESLint config with React/TypeScript config
- Add ignores for build directories (dist, .next, out)
- Install eslint-plugin-react and eslint-plugin-react-hooks
- Disable pre-existing rule violations for compatibility

Co-authored-by: benscobie <[email protected]>

- Move LibrariesContextProvider and ToastContainer from main.tsx to Layout component
- Wrap <Outlet /> with LibrariesContextProvider to match Next.js structure
- Replace all process.env.NEXT_PUBLIC_BASE_PATH with import.meta.env.VITE_BASE_PATH
- Fix ApiHandler to use import.meta.env instead of process.env

This resolves the "process is not defined" error and ensures proper context availability for all routes.

Co-authored-by: benscobie <[email protected]>

- Restructure router to make settings routes nested under /settings parent
- Add Outlet to SettingsWrapper to render child routes
- All settings sub-pages (plex, sonarr, etc.) are now children of settings route
- Settings index route redirects to /settings/main

This ensures the settings tabs remain visible when navigating between different settings pages.

Co-authored-by: benscobie <[email protected]>

- Remove NextPage type imports from all page files
- Remove all 'next' package imports
- Delete old Next.js page wrapper files in pages/ directory
- Keep only DocsPage.tsx and PlexLoadingPage.tsx which are used by router
- Remove pages/_app.tsx, pages/rules, pages/collections, pages/overview, pages/settings, etc.

All pages now use standard React function components without Next.js types.

Co-authored-by: benscobie <[email protected]>

Replaced all instances of `document.title =` with React Helmet's `<Helmet><title>` component across all pages and settings components:

**Pages Updated:**
- Overview: Maintainerr - Overview
- Rules: Maintainerr - Rules
- Collection: Maintainerr - Collections
- AddModal: Maintainerr - Overview

**Settings Pages Updated:**
- Main: Maintainerr - Settings - General
- Plex: Maintainerr - Settings - Plex
- Sonarr: Maintainerr - Settings - Sonarr
- Radarr: Maintainerr - Settings - Radarr
- Overseerr: Maintainerr - Settings - Overseerr
- Jellyseerr: Maintainerr - Settings - Jellyseerr
- Tautulli: Maintainerr - Settings - Tautulli
- Notifications: Maintainerr - Settings - Notifications
- Jobs: Maintainerr - Settings - Jobs
- Logs: Maintainerr - Settings - Logs
- About: Maintainerr - Settings - About

This provides a more React-compliant way to manage page titles and allows better integration with the existing Helmet setup in the Layout component. All titles are now managed declaratively through JSX rather than imperatively through the DOM API.

Result: Zero lint errors, build succeeds in 5.9s

Co-authored-by: benscobie <[email protected]>

- Updated .github/copilot-instructions.md to reflect Vite + React Router migration
  - Changed "Next.js frontend" to "Vite + React Router frontend"
  - Updated frontend tech stack (Vite, React Router, React Helmet, etc.)
  - Updated frontend patterns (routing, navigation, code splitting)
  - Updated UI structure to show router.tsx and main.tsx instead of pages router
  - Updated performance considerations to mention Vite HMR instead of Next.js SSG
- Removed ui/README.md (outdated Next.js documentation)

All documentation now accurately reflects the current Vite + React Router architecture.

Co-authored-by: benscobie <[email protected]>

… of state-based navigation

**Rules Routing:**
- /rules - List all rules
- /rules/new - Create a new rule
- /rules/edit/:id - Edit an existing rule

**Collections Routing:**
- /collections - List all collections
- /collections/:id - View collection (default to Media tab)
- /collections/:id/exclusions - View collection exclusions
- /collections/:id/info - View collection info

**Changes:**
- Created RulesListPage.tsx - Rules list with navigation to new/edit
- Created RuleFormPage.tsx - Unified form for creating/editing rules (uses :id param)
- Created CollectionsListPage.tsx - Collections list with navigation to details
- Created CollectionDetailPage.tsx - Collection wrapper with tabs and nested routes
- Created CollectionMediaPage.tsx - Media tab content
- Created CollectionExclusionsPage.tsx - Exclusions tab content
- Created CollectionInfoPage.tsx - Info tab content
- Updated router.tsx with nested routes structure
- Removed state-based navigation from original components

**Navigation Improvements:**
- URLs now reflect current page/tab (better for bookmarking, sharing, browser back/forward)
- Clicking a collection navigates to /collections/:id instead of showing modal
- Collection tabs use URL paths instead of state
- Rules create/edit use URL paths instead of modal state
- Browser back button works correctly with proper routing

Build succeeds in 6.2s, zero lint errors (pre-existing warnings unchanged).

Co-authored-by: benscobie <[email protected]>

**Bug Fixes:**

1. **Rule Edit Page Crash** - Fixed "can't access property toString, libraryId is undefined" error:
   - Added optional chaining in AddModal component when accessing editData.libraryId
   - Added error handling to RuleFormPage to catch API failures and redirect to rules list
   - Used editData?.libraryId instead of editData.libraryId to prevent undefined access

2. **Collection Tab Active State** - Fixed tabs not highlighting correctly when navigating:
   - Changed from using URL params (:tab) to using location.pathname to determine active tab
   - Added getCurrentTab() function that checks the full path to identify active tab
   - Media tab: /collections/:id (index route)
   - Exclusions tab: /collections/:id/exclusions
   - Info tab: /collections/:id/info
   - Now correctly highlights the active tab based on current URL

**Testing:**
- Build succeeds in 7.84s
- Zero lint errors (only pre-existing warnings remain)
- Rule edit page handles missing data gracefully
- Collection tabs now show correct active state when navigating

Both bugs are now resolved and the application works correctly.

Co-authored-by: benscobie <[email protected]>

Fixed "can't access property 'map', props.editData.rules is undefined" error by adding optional chaining to all editData property accesses:

- props.editData?.rules instead of props.editData.rules for the map operation
- Added nullish coalescing (?? true) for useRules and isActive to handle undefined
- Added optional chaining for collectionId and id properties

This ensures the rule edit page handles all cases where editData properties might be undefined, preventing crashes when loading rule data.

Build succeeds in 5.89s, zero lint errors.

Co-authored-by: benscobie <[email protected]>

Co-authored-by: benscobie <[email protected]>