Rules Hub
Code Ruleset
← Back to all rules
Rule priority, scope & exceptions
Use this to align rules with the senior-level structure (P0/P1/P2, scope, exceptions/tradeoffs).
backend ruleP2stack specificStack: Node.js / npm
dependenciespackage-jsontooling
Put type-only packages in devDependencies
Place type packages according to build and published declaration needs; they are not universally dev-only.
PR: hegnar-user-ws · org-mining-hist-2026-06Created: Jun 18, 2026
Bad example
Old codejson
| 1 | "dependencies": { |
| 2 | "@types/lodash": "^4.14.198" |
| 3 | } |
Explanation (EN)
An application runtime-only installation need not carry unused development type packages.
Objašnjenje (HR)
Good example
New codejson
| 1 | "devDependencies": { |
| 2 | "@types/lodash": "^4.14.198" |
| 3 | } |
Explanation (EN)
Objašnjenje (HR)
Notes (EN)
For an application, keep build/test-only type packages in devDependencies when the build stage installs them and runtime output does not need them.
Exceptions / Tradeoffs (EN)
Published libraries whose emitted declarations reference another type package must make those declarations resolvable for consumers, often through dependencies. A production image building source may also require build dependencies.