[Frontend] tsconfig.json — enable noUncheckedIndexedAccess and noUnusedLocals

[ogazboiz]

Join the discussion on Telegram

Why this matters

frontend/tsconfig.json has \"strict\": true but is missing the safer-strict family that the backend tsconfig already enables:

Backend backend/tsconfig.json has:

\"noUncheckedIndexedAccess\": true,
\"exactOptionalPropertyTypes\": true,

Frontend has neither. The frontend has many obj[key] accesses (in localStorage parsing, stream maps, etc.) that silently assume the value exists. Turning on noUncheckedIndexedAccess is a great win for catching real bugs (e.g. fractionalPart.length on a possibly-undefined value in frontend/src/lib/amount.ts:98 — likely unreachable but no longer relies on luck).

noUnusedLocals would also surface the dead constant in frontend/src/lib/dashboard.ts:46 (filed separately) and any others.

Acceptance criteria

• Add noUncheckedIndexedAccess: true to frontend/tsconfig.json
• Add noUnusedLocals: true
• Fix or annotate the call sites the new check surfaces — expect 5-15 small changes
• npm run build passes
• Do NOT also add exactOptionalPropertyTypes in the same PR (too noisy; separate issue)

Files to touch

• frontend/tsconfig.json
• whichever frontend/src/** files the type-checker now complains about

Out of scope

• Enabling exactOptionalPropertyTypes (deferred to separate issue)

[RaymondAbiola]

@RaymondAbiola has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, I’d like to work on this issue. I have experience with rust, Solidity, frontend, and backend development, and I’m confident I can deliver a clean solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @RaymondAbiola to this issue.

[oscar24357]

@oscar24357 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

hello maintainer, can you please assign this issue to me, i would like to work on it, thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @oscar24357 to this issue.

[Emmy6654]

@Emmy6654 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

pls i will love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Emmy6654 to this issue.

[shogun444]

@shogun444 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hello Maintainer, I'm excited about this issue and would like to be assigned. I'll document my approach in the PR description so the team can follow my reasoning and suggest improvements early.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @shogun444 to this issue.

[khanavi272-spec]

@khanavi272-spec has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @khanavi272-spec to this issue.

[Benedict315]

@Benedict315 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

please assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Benedict315 to this issue.

[drips-wave]

Congratulations, @shogun444! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @shogun444: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊