[BUG] tsc --noEmit fails on main with 42 errors — unclosed interface blocks every commit

[SakethSumanBathini]

Summary

npx tsc --noEmit fails on clean main @ a5b5a9e. Because husky runs it pre-commit, no commit can be made without --no-verify.

The first error stops the compiler outright:

src/types/index.ts(60,1): error TS1131: Property or signature expected.

Cause

OrgStats is never closed — the next interface starts inside it:

export interface OrgStats {
  prsCount?: number;
  issuesCount?: number;
  commitsCount?: number;
  reviewsCount?: number;      // <- line 59, no closing brace
export interface GistItem {   // <- line 60

Introduced by dd1672b ("Merge branch 'main' into feat/Organization-Specific-Contribution-Stats") — a merge that dropped the brace where OrgStats and GistItem (from #793) met.

It's worse underneath

Adding the brace lets the compiler continue, and it then reports 42 errors across 10 files:

src/app/api/[username]/story/route.ts   'fetchProfileSnapshot' is not exported (did you mean 'getProfileSnapshot'?)
src/app/api/[username]/view/route.ts    'checkRateLimit' is not exported from '@/lib/rate-limit'
src/app/explore/page.tsx                Cannot find name 'describeFilters'  (x2)
src/components/profile/GistList.tsx
src/components/profile/ProfileReposSection.tsx    GitHubRepo missing stars, forks, languageColor, url
src/components/profile/ProfileView.tsx
src/lib/__tests__/open-source-story.test.ts
src/lib/__tests__/org-stats.test.ts

Several look like the same merge losing or renaming exports rather than independent bugs.

Impact

Every contributor needs --no-verify to commit, which defeats the hook — and a hook people routinely bypass stops catching anything, including the next unclosed brace.

Suggested fix

The one-line brace first, as its own PR, since it unblocks the compiler and lets everyone see the rest. The remaining 41 are probably best triaged by whoever merged the two features involved, since most look like merge fallout rather than genuine type mistakes.

Happy to send the brace fix immediately if that's useful.

[github-actions]

Hey @SakethSumanBathini, thanks for opening this issue! 👋

Before anyone starts working on this, please comment below explaining your approach — what you plan to do and how you plan to do it.

A few things to keep in mind:

• ✍️ Write the explanation yourself — don't paste AI-generated text. We want to understand how you think about the problem.
• 📌 Wait to be assigned before you start coding. This avoids two people solving the same thing at once.
• 📋 Read CONTRIBUTING.md if you haven't already.

Once a maintainer reviews your approach and assigns the issue to you, you're good to go. Looking forward to it! 🚀

[PRODHOSH]

go ahead @SakethSumanBathini

[SakethSumanBathini]

Update: the unclosed OrgStats brace is already fixed on main @ 87724b8 — someone closed it in the last couple of days, so that part is done.

The compiler now runs to completion and reports 45 errors across 13 files:

File	Errors
components/profile/ProfileView.tsx	8
lib/org-stats.ts + its test	8
lib/__tests__/open-source-story.test.ts	4
lib/refresh-profile.ts	2
app/explore/page.tsx	2
profile-data.ts, language-treemap.ts, badges.test.ts, ProfileReposSection.tsx, GistList.tsx, view/route.ts, story/route.ts	1 each

I've sent a PR for the explore/page.tsx pair — a missing describeFilters import, genuinely one line.

The other 43 I don't think I should fix, and it's worth saying why rather than just leaving them.

story/route.ts looked like a rename: it imports fetchProfileSnapshot and the compiler suggests getProfileSnapshot. I tried it — the file goes from 1 error to 5, because getProfileSnapshot returns SnapshotRow and the caller reads username, stats, repos and score, none of which exist on it. So the two were written against different data shapes, and picking one is a decision about what the endpoint is meant to return.

view/route.ts is similar: it calls checkRateLimit(key, { maxRequests: 10, windowMs: 60000 }), and that signature doesn't exist anywhere in rate-limit.ts. The real exports are checkRefreshRateLimit(request) and checkDeveloperInsightsRateLimit(request), both wrapping checkNamedRateLimit(request, namespace). Making the call site work means either adding a namespace or adding a new export — again a design call.

The ProfileView.tsx cluster is 8 instances of the same thing: indexing LANGUAGE_COLORS with a string, which needs an index signature or a lookup helper. That one is mechanical but touches a shared constant, so it's worth the owner's eye.

My suggestion is to route the clusters to whoever merged the features they came from — most trace to the org-stats and open-source-story merges — rather than have one person guess at all of them. Happy to take any specific cluster if you'd rather assign it.