ci: make typecheck job actually type-check the project - #217
Merged
Conversation
📝 WalkthroughWalkthroughChangesAuthentication test alignment
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ktursunov
approved these changes
Jul 24, 2026
typecheck ran `tsc --noEmit`, which in non-build mode ignores project references. The root tsconfig lists `"files": []`, so the command type-checked zero files and every type error in `src` (including tests) passed CI silently — caught only by a local `tsc -b` in the build. Switch to `tsc -b` so the typecheck job checks the same graph as the build. `noEmit` in tsconfig.app.json keeps it emit-free. Signed-off-by: Aleksandr Barkhatov <pm@aleks.bar>
aleksdotbar
force-pushed
the
fix/ci-typecheck-build-mode
branch
from
July 24, 2026 07:40
3474916 to
a83fbc9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The CI
typecheckjob rantsc --noEmit. In non-build mode,tscdoes not follow projectreferences, and the roottsconfig.jsondeclares"files": []. Result: the command type-checks zero files and exits 0 regardless of type errors anywhere insrc.Every type error since this config landed was invisible to CI — caught only by a developer running
tsc -blocally (viapnpm build). This is how type-breaking changes have reachedmaingreen (e.g. the missingcsrfTokenSession fixtures fixed in #216).Proof
Injecting
const x: number = "s"intosrc/auth/types.ts:tsc --noEmit(old CI command) → exit 0, error missedtsc -b(build) → exit 2, error caughttsc --noEmit --listFilesloads 0 files fromsrc.Fix
typecheck→tsc -b, so the job type-checks the same project graph as the build.noEmit: trueintsconfig.app.jsonkeeps it emit-free.🤖 Generated with Claude Code