Add a typecheck script and wire it into CI ahead of lint/test/build

[Jagadeeshftw]

📌 Description

package.json's scripts cover dev, build, start, lint, test, and test:coverage, but there's no standalone tsc --noEmit script — type errors are currently only caught incidentally during next build's own type-checking pass, mixed in with the build step rather than as a fast, isolated CI check.

🧩 Requirements and context

• Add a typecheck script to package.json running tsc --noEmit (or the project's equivalent strict-check invocation).
• Wire the new script into the CI workflow so it runs early (before or alongside lint/test), giving fast feedback on type errors without waiting for a full next build.
• No change to the existing build script's own type-checking behavior.

🛠️ Suggested execution

• Add a "typecheck": "tsc --noEmit" entry to package.json's scripts.
• Update the repository's CI workflow (the pull-request workflow covered elsewhere in this project's issue backlog, or whichever workflow file currently runs lint/test/build) to add a typecheck step.

✅ Acceptance criteria

• A typecheck script exists in package.json and runs cleanly against the current codebase.
• CI runs the typecheck step on pull requests.

🔒 Security notes

No new attack surface; a developer-tooling/CI task.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[OluRemiFour]

Hi Maintainer,
Interested in working on this issue. I'll implement the requested changes and ensure everything is properly tested before submission.

[Chigybillionz]

Hi! I'd like to work on this issue.

This is a useful CI improvement. Running type checking as a dedicated step provides much faster feedback than waiting for "next build", while keeping build responsibilities unchanged.

My plan is to:

• Add a "typecheck" script to "package.json" using "tsc --noEmit".
• Update the CI workflow to execute the typecheck step before or alongside lint and tests.
• Verify the current codebase passes the new check and ensure the existing build workflow remains unchanged.

I have experience working with TypeScript, Next.js, and GitHub Actions, and I'll make sure the implementation is minimal, consistent with the project's existing CI setup, and doesn't introduce any behavioral changes beyond the new validation step.

GitHub: https://github.com/chigybillionz

[raizo07]

Hello, I'd like to be assigned to work on this issue

ETA: 3 hours

[Sammygee12]

Hello Maintainer, I'd like to work on this issue. I have experience with frontend development and state management, and I can implement this. Please consider assigning it to me.

[grantfox-oss]

🦊 GrantFox — @raizo07 has been assigned to this issue as part of the Official Campaign | FWC26 campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #188)
2. Your PR will be reviewed by the AnchorNet-Org maintainers

Good luck! Track your progress on GrantFox.