Enable incremental caches for tsc and ESLint in frontend#342
Merged
Conversation
Add TypeScript incremental build info and ESLint --cache to speed up repeated type-check and lint runs. Caches are written under node_modules/.cache (already git-ignored). No behavior change.
Contributor
There was a problem hiding this comment.
Pull request overview
Speeds up repeated frontend developer/CI checks by enabling persistent incremental caches for TypeScript type-checking and ESLint runs within frontend/, keeping cache artifacts under node_modules/.cache.
Changes:
- Enabled TypeScript incremental compilation cache via
incremental+tsBuildInfoFileinfrontend/tsconfig.json. - Enabled ESLint’s cache and routed it to
./node_modules/.cache/eslint/via thelintscript.
Show a summary per file
| File | Description |
|---|---|
| frontend/tsconfig.json | Adds TS incremental build-info cache output under node_modules/.cache/tsc/. |
| frontend/package.json | Updates lint to use ESLint cache stored under node_modules/.cache/eslint/. |
Copilot's findings
- Files reviewed: 2/2 changed files
- Comments generated: 1
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.
What
Purely incremental-cache configuration to speed up repeated TypeScript type-checking and ESLint runs in
frontend/. No behavior change.Changes (limited to
frontend/)tsconfig.json: added"incremental": trueand"tsBuildInfoFile": "./node_modules/.cache/tsc/tsconfig.tsbuildinfo". The build-info path lives insidenode_modules, so it is naturally git-ignored.package.json: lint script changed fromeslint .toeslint . --cache --cache-location ./node_modules/.cache/eslint/.Git-ignore
Both caches write under
node_modules/.cache, andnode_modulesis already ignored infrontend/.gitignore— no.gitignorechanges needed. Verified the cache artifacts are not tracked.Verification
All steps run in
frontend/afteryarn install:yarn tscyarn lintyarn buildThe second
tscandlintruns are clearly faster thanks to the cache. Build (vite build) still succeeds and is unaffected.Scope note
Intentionally minimal — only
frontend/tsconfig.jsonandfrontend/package.json. Does not touch the in-flight Yarn package-manager migration or the Android/Gradle changes. Theyarn.lockregeneration produced by a local install was reverted to avoid churn with the migration PR.