Repository navigation
perf(build): limit strict production TypeScript checks to shipped code - #91
Merged
Merged
Conversation
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.
Motivation
Production Vercel build logs show ~58 seconds spent in TypeScript checking. The root tsconfig selects 946 tracked TS/TSX files, including 147 test files and development-only scripts that don't ship in the Next.js app.
Changes
tsconfig.build.jsonextending the existing stricttsconfig.json, excluding tests, development scripts, Firebase Functions (which have their own TypeScript compilation CI), and lint tooling..tsbuildinfocache to avoid collisions with local dev diagnostics.NODE_ENV=productionwhile preserving the full root config in development, withignoreBuildErrors: false.Safety and verification
pnpm lint/pnpm typecheckscripts.Scope
No Vercel preview or manual release.