https://prule.github.io/pauls-blog/tags/performance/Recent content in Performance on Pauls BlogHugoen-usFri, 26 Jun 2026 20:28:52 +1000https://prule.github.io/pauls-blog/post/coding/2026/switching-to-fnm/Fri, 26 Jun 2026 00:00:00 +1000https://prule.github.io/pauls-blog/post/coding/2026/switching-to-fnm/<p><code>fnm</code> and <code>nvm</code> are tools for managing node installations. This is useful for ensuring the correct version of node is used for each project.</p> <p><code>fnm</code> is built in Rust. It&rsquo;s orders of magnitude faster than <code>nvm</code>, cross-platform, and fully compatible with existing <code>.nvmrc</code> and <code>.node-version</code> files.</p> <h2 id="why-switch">Why Switch?</h2> <p><code>nvm</code> is a massive shell script. It sources itself every time you open a new terminal tab. This overhead becomes noticeable, often adding 300-500ms to shell startup times.</p>https://prule.github.io/pauls-blog/post/coding/2026/why-switch-to-pnpm/Mon, 08 Jun 2026 00:00:00 +1000https://prule.github.io/pauls-blog/post/coding/2026/why-switch-to-pnpm/<p>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.</p> <p><strong>pnpm</strong> (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 <code>node_modules</code>, pnpm makes dependency resolution fast, strict, and disk-efficient.</p>