Installing packages (dependencies vs devDependencies) in Node.js - Why You Should Know This

The Big Idea

Ever wonder why some projects are bloated with unnecessary tools after deployment?

The Scenario

Imagine you build a Node.js project and manually download every library you need, then copy them into your project folder. You also mix tools needed only during development with those needed in production.

The Problem

This manual way is slow, confusing, and risky. You might forget to include a library, or accidentally ship development tools to users, making your app bigger and slower.

The Solution

Using package managers with dependencies and devDependencies lets you clearly separate what your app needs to run from what you need to build it. This keeps your project organized and efficient.

Before vs After

✗ Before

Download lodash and build tools manually and copy to project folder

✓ After

npm install lodash --save
npm install eslint --save-dev

What It Enables

This separation makes your app lighter in production and your development smoother and safer.

Real Life Example

When deploying a website, only the runtime libraries are included, while testing and building tools stay behind, speeding up deployment and reducing errors.

Key Takeaways

Manually managing packages is slow and error-prone.

Dependencies are for runtime; devDependencies are for development only.

Using this separation keeps projects clean, efficient, and easier to maintain.