<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NodeJS on Pauls Blog</title><link>https://prule.github.io/pauls-blog/tags/nodejs/</link><description>Recent content in NodeJS on Pauls Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 08 Jun 2026 20:58:00 +1000</lastBuildDate><atom:link href="https://prule.github.io/pauls-blog/tags/nodejs/index.xml" rel="self" type="application/rss+xml"/><item><title>Why You Should Switch to pnpm</title><link>https://prule.github.io/pauls-blog/post/coding/2026/why-switch-to-pnpm/</link><pubDate>Mon, 08 Jun 2026 00:00:00 +1000</pubDate><guid>https://prule.github.io/pauls-blog/post/coding/2026/why-switch-to-pnpm/</guid><description>&lt;p&gt;If you are still using npm or Yarn Classic, you are wasting gigabytes of local storage, slowing down your CI/CD pipelines, and opening the door to silent dependency bugs.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;pnpm&lt;/strong&gt; (performant npm) solves these issues out of the box. By replacing file duplication with a single, content-addressable store and using hard links to assemble &lt;code&gt;node_modules&lt;/code&gt;, pnpm makes dependency resolution fast, strict, and disk-efficient.&lt;/p&gt;</description></item></channel></rss>