I Kept Hearing "Just Use pnpm" and Kept Ignoring It

Honestly, I thought it was just another tool people hyped for no reason. I had npm, and it worked.

Then one day, I noticed my disk storage was critically low.

Like... where did all my space go?

I had no idea.

Started digging around, asked ChatGPT, and it turned out the culprit was node_modules.

Multiple projects. Each with its own massive node_modules folder. Just quietly eating up disk space.

That's when I finally tried pnpm.

It took about 5 minutes to switch.

And I actually sat down to understand why it was different—because I don't like adopting tools just because someone on the internet told me to.

The Simple Difference

npm

npm saves a full copy of every package inside each project.

So if you have 10 projects using React, you end up with 10 separate copies sitting on your disk doing absolutely nothing useful.

pnpm

pnpm is smarter.

It stores packages in one central location on your computer and creates links from each project to that shared store.

That means:

• No duplicate files
• Significantly less disk usage
• Faster installs
• Better cache efficiency

Since the packages already exist in the global store, installing dependencies often feels noticeably faster.

The Unexpected Benefit: Strict Dependencies

One thing I didn't expect was how strict pnpm is about dependencies.

At first, that sounds annoying.

But it actually prevents those frustrating situations where:

"It works on my machine, but breaks everywhere else."

You know the ones.

By enforcing proper dependency declarations, pnpm helps catch hidden issues before they become production problems.

Should Everyone Switch?

For a small project?

Probably not.

npm is perfectly fine, and there's no reason to switch just for the sake of switching.

But if you're: