Dependencies vs devDependencies in Node.js: Key Differences and Usage

In Node.js, dependencies are packages your project needs to run in production, while devDependencies are only needed during development and testing. This distinction helps keep production installs lean and efficient.

Quick Comparison

This table summarizes the main differences between dependencies and devDependencies in Node.js projects.

Factor	dependencies	devDependencies
Purpose	Required for running the app	Required only for development and testing
Installed with npm install --production	Yes	No
Examples	Express, React	Testing tools, build tools like Babel
Included in package.json	Under dependencies	Under devDependencies
Impact on production size	Increases size	Does not increase production size

Key Differences

dependencies are packages your app needs to work properly when it runs in production. For example, if your app uses Express to handle web requests, Express must be in dependencies. These packages are installed when you run npm install normally or with the --production flag.

devDependencies are packages only needed during development, like testing frameworks, code linters, or build tools. They help you write and test your code but are not needed when the app runs live. These packages are installed only when you run npm install without the --production flag.

Keeping development tools separate from runtime packages helps reduce the size of your production environment and avoids shipping unnecessary code.

Code Comparison

Here is an example showing how to add a package as a dependency in your Node.js project.

bash

npm install express

// This adds Express to the dependencies section in package.json
// Your package.json will include:
// "dependencies": {
//   "express": "^<version>"
// }

Output

added 50 packages, and audited 50 packages in 2s

found 0 vulnerabilities

devDependencies Equivalent

Here is how you add a package as a devDependency for development only.

bash

npm install --save-dev jest

// This adds Jest to the devDependencies section in package.json
// Your package.json will include:
// "devDependencies": {
//   "jest": "^<version>"
// }

Output

added 30 packages, and audited 30 packages in 1s

found 0 vulnerabilities

When to Use Which

Choose dependencies when the package is essential for your app to run in production, like frameworks or libraries your code imports at runtime. Choose devDependencies when the package is only needed during development, such as testing tools, build systems, or code formatters. This keeps your production environment clean and efficient.

Key Takeaways

Use dependencies for packages needed at runtime in production.

Use devDependencies for packages only needed during development and testing.

Installing with npm install --production skips devDependencies to reduce production size.

Keep your package.json organized by separating runtime and development packages.

This separation improves app performance and deployment efficiency.