typescript-devdependencies

TypeScript and @types packages should be in devDependencies because they are development-only tools used for type checking, not runtime execution. Keeping them separate ensures production bundles remain lean and type definitions stay accurate.

To audit and move TypeScript and @types, categorize them under devDependencies in package.json. This skill provides installation commands and example configurations to enforce the separation and verify the updated setup using npm install.

Separating dependencies from devDependencies is critical for library publishing. It preserves runtime dependencies separately from type definitions, ensuring consumers install only necessary runtime packages while keeping typings accurate and available.

You need to separate TypeScript types from runtime dependencies during initial project setup, library publishing, and dependency audits. This prevents development-only type definitions from inflating production runtime bundles.

The best way to keep runtime dependencies lean is to enforce correct placement of TypeScript and @types packages into devDependencies. This ensures type definitions are available during development without adding overhead to production.