Task Description
Migrate the template app from the current mixed JavaScript/TypeScript ESLint configuration (juno-typescript.mjs) to the new pure TypeScript configuration (vite-react-ts.mjs). This will eliminate the need for
rule override workarounds and enable strict TypeScript checking aligned with Vite's default setup.
Sub-tasks
Related Issues
Epic: #1565 - ESLint Configuration Migration to Vite-React-TypeScript Standards
Additional Context
Current State:
- Template app uses mixed JS/TS configuration from
juno-typescript.mjs
- Requires 15-20 TypeScript rule overrides as workarounds
- Mixing
pluginJs.configs.recommended with tseslint.configs.recommendedTypeCheckedOnly causes conflicts
Target State:
- Use new pure TypeScript configuration
vite-react-ts.mjs
- Minimal overrides (≤5 rules) with justification comments
- Strict TypeScript checking enabled
- Aligned with Vite's default ESLint setup
- Better type safety and developer experience
Migration Pattern:
This follows the epic's three-phase approach. Template app is one of 7 apps being migrated in parallel during Phase 2. The old config will be retained until all apps/packages complete migration (Phase 3).
Task Description
Migrate the template app from the current mixed JavaScript/TypeScript ESLint configuration (
juno-typescript.mjs) to the new pure TypeScript configuration (vite-react-ts.mjs). This will eliminate the need forrule override workarounds and enable strict TypeScript checking aligned with Vite's default setup.
Sub-tasks
eslint.config.mjsto import and use the newvite-react-ts.mjsconfiguration from@cloudoperators/juno-configjuno-typescript.mjsconfigurationRelated Issues
Epic: #1565 - ESLint Configuration Migration to Vite-React-TypeScript Standards
Additional Context
Current State:
juno-typescript.mjspluginJs.configs.recommendedwithtseslint.configs.recommendedTypeCheckedOnlycauses conflictsTarget State:
vite-react-ts.mjsMigration Pattern:
This follows the epic's three-phase approach. Template app is one of 7 apps being migrated in parallel during Phase 2. The old config will be retained until all apps/packages complete migration (Phase 3).