[Task](Heureka): Migrate to new Vite-React-TypeScript ESLint configuration

[ArtieReus]

Task Description

Migrate the Heureka application from the legacy juno-typescript.mjs ESLint config (which contains mixed JavaScript/TypeScript rules) to the new vite-react-ts.mjs configuration that provides pure TypeScript
linting rules without JavaScript rule interference.

Goals:

• Switch Heureka's ESLint configuration to use the new vite-react-ts.mjs config
• Fix all TypeScript linting violations that surface after the migration
• Achieve maximum 5 rule overrides with justification comments
• Eliminate all workaround rule disables that were required with the old config
• Ensure pnpm lint passes successfully

Sub-tasks

• Update Heureka's eslint.config.mjs to import and use the new vite-react-ts.mjs configuration
• Run pnpm lint to identify all violations
• Fix easy violations (unused variables, naming conventions)
• Fix medium complexity violations (type assertions, explicit any usage)
• Fix hard violations (unsafe member access, type-unsafe calls)
• Document any necessary rule overrides with justification comments (max 5)
• Remove all workaround disables from old config
• Verify pnpm lint passes successfully
• Verify pnpm typecheck passes
• Create changeset for the changes

Related Issues

Part of ESLint Configuration Migration Epic #1565

Additional Context

This is one of 7 applications being migrated as part of the project-wide effort to eliminate JavaScript/TypeScript rule conflicts in shared config and enable strict TypeScript checking across all apps.

Migration Approach:
Fix violations category-by-category in order of complexity:

• Easy: unused variables, naming conventions
• Medium: type assertions, explicit any usage
• Hard: unsafe member access, type-unsafe calls

Each category can potentially be handled in separate pull requests if the scope is large.

Acceptance Criteria:

• Heureka uses vite-react-ts.mjs instead of juno-typescript.mjs
• pnpm lint passes with no errors
• Maximum 5 rule overrides with clear justification comments
• All workaround disables from old config are removed
• TypeScript strict checking is enabled without violations

[hodanoori]

Heureka ESLint Migration — Violation Report

Config: juno-typescript.mjs → vite-react-ts.mjs
Total: 319 problems — 315 errors, 4 warnings
Affected files: 49

---

Violations by Rule

Count	Rule	Category	Complexity
82	@typescript-eslint/no-unsafe-member-access	Unsafe any access	Hard
57	@typescript-eslint/no-unsafe-assignment	Unsafe any access	Hard
45	@typescript-eslint/no-explicit-any	Type safety	Medium
25	@typescript-eslint/require-await	Async correctness	Easy
24	@typescript-eslint/no-unsafe-call	Unsafe any access	Hard
18	@typescript-eslint/no-floating-promises	Async correctness	Medium
16	@typescript-eslint/no-unsafe-return	Unsafe any access	Hard
13	@typescript-eslint/no-redundant-type-constituents	Type hygiene	Easy
8	react-refresh/only-export-components	React	Easy
8	setState sync in effect (react-hooks)	React	Medium
5	@typescript-eslint/no-unsafe-argument	Unsafe any access	Hard
4	react-hooks/exhaustive-deps	React	Medium
3	no-extra-boolean-cast	JS hygiene	Easy
2	@typescript-eslint/no-unnecessary-type-assertion	Type hygiene	Easy
2	Parsing error (parserOptions.project)	Config	Config fix
1	@typescript-eslint/ban-ts-comment	Type hygiene	Easy

---

Violations by File

File	Errors	Warnings
src/components/Service/ImageDetails/ImageIssuesList/index.tsx	high	—
src/components/Service/ImageDetails/RemediationHistoryPanel/index.tsx	high	1
src/components/Service/ImageDetails/FalsePositiveModal/index.tsx	high	—
src/components/Service/ImageDetails/RiskAcceptanceModal/index.tsx	high	—
src/components/Vulnerabilities/VulnerabilitiesList/index.tsx	medium	—
src/components/Services/ServicesList/index.tsx	medium	—
src/components/Service/ImageDetails/ImageVersionOccurrences.tsx	medium	—
src/components/Service/ImageVersionDetails/ImageVersionOccurrences.tsx	medium	—
src/generated/graphql.ts	medium	—
src/store/StoreProvider.tsx	medium	—
src/utils.ts	medium	—
src/api/fetchVulnerabilities.tsx	2	—
codegen.ts	1	—
vite.config.ts	parsing error	—
vitest.config.ts	parsing error	—
(34 additional test/component files)	low	—

---

Grouping by Fix Strategy

Easy — Remove / rename (35 violations)

• 25 require-await — remove async from functions/arrows with no await (mostly test mocks)
• 3 no-extra-boolean-cast — remove redundant !!
• 3 no-redundant-type-constituents (subset) — simplify union types
• 2 no-unnecessary-type-assertion — remove redundant as Type casts
• 1 ban-ts-comment — replace @ts-ignore with @ts-expect-error in codegen.ts
• 1 Config fix — add vite.config.ts and vitest.config.ts to ignores in eslint.config.mjs

Medium — Proper typing required (75 violations)

• 45 no-explicit-any — replace any with proper types or unknown
• 18 no-floating-promises — add void operator or await
• 8 setState sync in effect — restructure effect logic
• 4 react-hooks/exhaustive-deps — fix dependency arrays

Hard — Unsafe any propagation (184 violations)

These mostly stem from untyped GraphQL responses and Zustand store selectors returning any.

• 82 no-unsafe-member-access
• 57 no-unsafe-assignment
• 24 no-unsafe-call
• 16 no-unsafe-return
• 5 no-unsafe-argument

Note: The bulk of hard violations trace back to two root causes:

1. GraphQL query results typed as any (codegen types not being used downstream)
2. Zustand store selectors with implicit any return types
   Fixing the root causes will resolve many downstream violations at once.

React — Component export pattern (13 violations)

• 8 react-refresh/only-export-components — non-component exports mixed with component files; fix by moving constants/utils to separate files
• 5 remaining react-hooks issues

---

Rule Override Candidates (max 5)

If fixing all hard violations is out of scope, these are the strongest override candidates with justification:

#	Rule	Justification
1	@typescript-eslint/no-redundant-type-constituents	GraphQL codegen produces these; fixing requires regenerating schema types
2	react-hooks/exhaustive-deps	Intentional omissions where including dep would cause infinite loops
3	react-refresh/only-export-components	Route files legitimately export both components and loader functions (TanStack Router pattern)