Skip to main content

RFC — Add explicit TypeScript devDependency pin (qontak-customer-fe)

Bucket item: A13 · Class: 🟡 Standard · Jira Story: pending mint (Task: TF-3557) · Epic: TF-3500

Source: Qontak_Stack_Analysis_Repository_Detail_July_2026, qontak-customer-fe tab, row 11.

Context / Problem​

TypeScript 5.8.3 is currently only a transitive dependency (pulled in via pnpm-lock.yaml / tsconfig.json, no direct pin in package.json) — it's only present as a peer dep of Nuxt/eslint tooling. The current major is TypeScript 6.0.x. Without a direct pin, an unrelated dependency bump could silently upgrade or downgrade the TypeScript version the whole codebase compiles against.

Proposed change​

Add an explicit typescript devDependency pin to package.json so the version is deterministic and not implicitly changed by unrelated dependency bumps.

Execution plan (call to action)​

  1. Add typescript to package.json devDependencies, pinned to the currently-working 5.8.x line (matching whatever transitive version is resolved today).
  2. Run pnpm install to confirm the lockfile resolves to the same version (no surprise bump).
  3. Run pnpm build and pnpm typecheck to confirm a clean pass with the pin in place.

Risks & rollback​

  • Risk: low — pinning to the already-resolved version should be a no-op for the build; the only risk is if the transitive resolution silently differs from what's assumed.
  • Rollback: remove the explicit devDependency entry; transitive resolution resumes.

Open questions​

  1. Should this pin move to TypeScript 6.0.x in the same pass, or strictly pin the current 5.8.x line and treat the major bump as separate, larger-blast-radius work?