Enforce Type Safety & Production Build Validation

[RUKAYAT-CODER]

Overview

Prevent runtime errors by enforcing strict TypeScript checks and successful production builds in CI.

Background

Dynamic routes, wallet providers, markdown rendering, and context-based state management must be type-safe to avoid production crashes.

Specifications

Modules to Create:

• Strict TypeScript configuration
• Build validation workflow

Tasks:

• Enable strict TypeScript mode
• Run tsc --noEmit in CI
• Run next build in CI
• Fail CI on type errors
• Prevent merge if build fails

Impacted Files:

• tsconfig.json
• package.json
• .github/workflows/ci.yml

Labels:

frontend, typescript, ci, quality, priority-high

Acceptance Criteria

• No implicit any
• Build succeeds in CI
• Type errors block PR merge
• Strongly typed components and hooks

🙌 Contribution Guidelines:
Assignment required before PR submission
Timeframe: 24–48 hours
PR description must include: Close #[issue-number]
Star the repo ⭐
For more context, please refer to the frontend README 🚀

Depend on #67

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[morelucks]

@morelucks has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello

I’d love to take ownership of this issue.

I’m comfortable working across smart contracts, backend services, and frontend integrations. I was a contributor in Drips Wave 1 and am also an experienced contributor and maintainer on OnlyDust across multiple projects. I bring hands-on experience in Rust, Soroban, Cairo, Solidity, and TypeScript.

I prioritize clean architecture, security, and maintainable code, and I’m confident I can deliver a complete, well-tested solution within 24 hours of assignment.

I’m ready to start immediatel. Please feel free to assign this issue to me.

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

[Queenode]

@Queenode has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

I would like to work on this issue, I will take appropriate approach, kindly assign

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

[laryhills]

@laryhills has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi, I’d like to apply for this issue! 🔒

About Me
I’m a frontend engineer with 6+ years of experience enforcing strict TypeScript and preventing production failures. I’ve enabled strict mode across large codebases, fixed type errors, and set up CI workflows that block merges on type/build failures.

Plan

• Enable strict TypeScript: set "strict": true in tsconfig.json, enable noImplicitAny, strictNullChecks, strictFunctionTypes
• Fix existing type errors: add return types to functions, type component props, resolve dynamic route types, strongly type context/hooks
• Create CI workflow in .github/workflows/ci.yml: add steps for tsc --noEmit (type checking), next build (production build)
• Fail CI on errors: ensure non-zero exit codes block PR merge, configure branch protection rules
• Add npm scripts: add type-check script for local development, pre-commit hooks optional
• Type dynamic routes: create route parameter types for wallet providers, markdown pages
• Type context/hooks: export types for all context providers, ensure strongly typed consumer components
• Test CI: verify workflow runs on PRs, catches type errors, prevents merge with failures
• Document: add guidelines for strict typing in contributing docs

Why Me
Strong expertise in TypeScript strict mode, migrating codebases to stricter configuration, and setting up CI quality gates. Experienced fixing type errors across large projects and preventing runtime crashes.
ETA
5-6 hours

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

[drips-wave]

Congratulations, @laryhills! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @laryhills: 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 issued 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 🌊

[drips-wave]

This issue has been completed by @laryhills as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @laryhills: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.