Keep the lint rule, remove its type-graph dependency

Linear rewrote its type-aware custom lint rules to use static analysis over the syntax tree.

Prompt

Evaluate and apply this CI technique to my repository: Keep the lint rule, remove its type-graph dependency.

Linear rewrote its type-aware custom lint rules to use static analysis over the syntax tree.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/lint-without-types.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How Linear used this technique

Read what Linear changed and follow the original sources.

Keep the lint rule, remove its type-graph dependency

Linear rewrote its type-aware custom lint rules to use static analysis over the syntax tree, so ESLint no longer builds the TypeScript type graph. API lint time fell 68% and full-repository lint time 55%.

Use it when: Type-aware lint setup dominates and equivalent syntax-only checks can be demonstrated.
Before applying it: A rule-by-rule equivalence ledger comes first. Keep genuinely type-aware rules in a required pass.

How Linear used this technique

Keep the lint rule, remove its type-graph dependency

Related techniques

Use a faster native linter without losing rules

Company Playbooks