DevInsight

A developer's field notes

Topic Archive

Tools

Developer tools, productivity apps, and open source tooling changes.

6 published posts belong to this topic.

Tools

The Spots That Quietly Collapse When You Drop eslintrc for Flat Config

When migrating from eslintrc to flat config, what breaks most often isn't the rules but plugin compatibility and the order in which configs are merged. As string-based extends disappears and gives way to arrays of objects, plugin registration, ignores handling, and editor integration all change. This article points out the places that fail silently during real migrations and offers criteria for deciding what to move first and what to throw away.

#ESLint#flat config#마이그레이션#린트
Tools

A Week Facing 2,731 Type Errors: The Reality Between Flipping strict On and Off

Enabling TypeScript's strict-family options all at once typically floods the build with thousands of type errors and stalls work. Based on a real project case, this compares each option's migration difficulty and blast radius, and lays out a step-by-step roadmap covering which order is safe to enable, what to fix automatically, and what has to be reviewed by hand.

#TypeScript#strict 모드#타입 안정성#레거시 코드
Tools

The Struggle of One Project's Upgrade from `any` Hell to `strict`

Suddenly enabling `strict` in a loosely-typed TypeScript project makes hundreds of errors pour out overnight. This article is a real migration log about enabling strict-family options one by one amid new feature development and bug fixes, weighing the difficulty and effect of each option to work out an optimal ordering. It covers everything from the `any` cleanup order to `strictNullChecks` and `noImplicitAny`, along with the real-world outages and regressions encountered along the way.

#TypeScript#strict#strictNullChecks#noImplicitAny
Tools

Only after deleting node_modules twice did I take another look at package managers

Choosing a package manager is a balancing act between three axes: install speed, disk usage, and phantom dependencies. In a standalone repo, even a careless choice rarely causes problems, but once you move to a monorepo, differences in hoisting strategies show up directly as CI time and disk blowups. This compares how npm, pnpm, and yarn each store and share dependencies, and lays out a decision flow for choosing a tool based on real conditions like team size and monorepo maturity.

#패키지매니저#pnpm#npm#yarn