Articles
Engineering writing on static analysis, ESLint, security, and AI-native developer tooling.
Filtered by tag #performance · clear filter
May 24, 2026Our linter reported 0 cycles. A cache bug hid 245 files at scale.Our import-next/no-cycle reported 0 cycles in next.js's 14K-file repo. oxlint reported 17. The same rule on a 33-file subset of the same repo found 5. The bug: a depth-truncated DFS cached files as 'known acyclic' that it had never finished exploring — and the cascade swallowed 245 files. Five lines fixed it. Here is why your AI-generated barrel files make this worse.#javascript#node#performance+122 min
Jan 2, 2026One INSERT Loop Made Our CSV Import 500x Slower. One ESLint Rule Catches It Before It Ships.A for-loop with an INSERT inside turned a 100ms bulk write into 50 seconds — 500x slower at 1,000 rows. The post-mortem, a reproduction you can run in 60 seconds, and pg/no-batch-insert-loop (CWE-1049): the ESLint rule that catches the N+1 shape before it ships.#node#database#performance+1138 min0
Dec 31, 2025Why eslint-plugin-import Takes 58 Seconds on 10,000 Files — And Where the Time Actually GoesA lint-performance post-mortem with the result JSON attached: 58.67s vs 11.26s on 10,000 files, and 148.59s vs 2.71s for no-cycle alone at 5,000 (eslint-plugin-import 2.32.0 vs eslint-plugin-import-next 2.3.3, measured 2026-01-02). What I can prove about the cause, and what I can't.#eslint#javascript#performance+17 min