<p>If you have been working with any node/javascript framework - be it React, Angular, Vue - there's an issue if you use <strong>npm</strong> or <strong>yarn</strong>.</p>
<p>It's something that happens in the background that you may not have noticed with every project you fire up - you <strong>redownload</strong> the packages in every instance.</p>
<p>What that means is that you end up having <strong>duplicates</strong> of the same packages in different folders on your machine.</p>
<p>I don't know about you, but I'm not okay with that...</p>
<h2 id="heading-why-pnpm">Why PNPM?</h2>
<p>Instead of redownloading the packages again, <strong>pnpm</strong> creates a central store where the packages are kept. </p>
<p>When you start up a new project, it checks if any of the packages required are already present on your system. If they are, it creates a reference to that store and doesn't redownload anything.</p>
<div class="embed-wrapper"><div class="embed-loading"><div class="loadingRow"></div><div class="loadingRow"></div></div><a class="embed-card" href="https://twitter.com/HemSays/status/1434921646083563525?s=20&amp;t=1eFwJ2bOBGJC8IhLrokygg">https://twitter.com/HemSays/status/1434921646083563525?s=20&amp;t=1eFwJ2bOBGJC8IhLrokygg</a></div>
<hr />
<h2 id="heading-conclusion">Conclusion</h2>
<p>Because I cannot do PNPM justice. Let me direct you to their site where they will do a much better job than I can:</p>
<blockquote>
<h2 id="heading-pnpmhttpspnpmiomotivation"><a target="_blank" href="https://pnpm.io/motivation">PNPM</a></h2>
</blockquote>
<hr />
<h3 id="heading-thank-you-for-reading-lets-connect">Thank you for reading, let's connect!</h3>
<p>Thank you for visiting this little corner of mine. Let's connect on <a target="_blank" href="https://twitter.com/Psypher1"><strong>Twitter</strong></a>, <a target="_blank" href="https://www.polywork.com/psypher1"><strong>Polywork</strong></a> and <a target="_blank" href="https://www.linkedin.com/in/jamesmidzi/"><strong>LinkedIn</strong></a></p>


If you have been working with any node/javascript framework - be it React, Angular, Vue - there's an issue if you use **npm** or **yarn**.

It's something that happens in the background that you may not have noticed with every project you fire up - you **redownload** the packages in every instance.

What that means is that you end up having **duplicates** of the same packages in different folders on your machine.

I don't know about you, but I'm not okay with that...

## Why PNPM?
Instead of redownloading the packages again, **pnpm** creates a central store where the packages are kept. 

When you start up a new project, it checks if any of the packages required are already present on your system. If they are, it creates a reference to that store and doesn't redownload anything.


%[https://twitter.com/HemSays/status/1434921646083563525?s=20&t=1eFwJ2bOBGJC8IhLrokygg]



---

## Conclusion
Because I cannot do PNPM justice. Let me direct you to their site where they will do a much better job than I can:

> ## [PNPM](https://pnpm.io/motivation)

---

###  Thank you for reading, let's connect!
Thank you for visiting this little corner of mine. Let's connect on [**Twitter**](https://twitter.com/Psypher1), [**Polywork**](https://www.polywork.com/psypher1) and [**LinkedIn**](https://www.linkedin.com/in/jamesmidzi/)


Why store separate copies of packages if you can have a `single` referencable one?

Do you care about the space on your disk?

Why You Should Consider PNPM As Your Package Manager

I am a polyglot and lover of languages of all kinds. I enjoy learning and sharing what I learn with anyone willing to listen. I try to do the best that I can today so I am better than I was yesterday.
