<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Npm on Nitin Kumar Singh</title><link>https://nitinksingh.com/tags/npm/</link><description>Recent content in Npm on Nitin Kumar Singh</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Nitin Kumar Singh. All rights reserved.</copyright><lastBuildDate>Fri, 03 Apr 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://nitinksingh.com/tags/npm/index.xml" rel="self" type="application/rss+xml"/><item><title>Why I Switched from npm to pnpm (And Why You Should Too)</title><link>https://nitinksingh.com/posts/why-i-switched-from-npm-to-pnpm-and-why-you-should-too/</link><pubDate>Fri, 03 Apr 2026 10:00:00 +0530</pubDate><guid>https://nitinksingh.com/posts/why-i-switched-from-npm-to-pnpm-and-why-you-should-too/</guid><description>&lt;p&gt;If you write JavaScript or TypeScript professionally, you&amp;rsquo;ve used npm. It ships with Node.js, it&amp;rsquo;s everywhere, and for years it was the only game in town. But after running npm on real-world projects — enterprise monorepos, Next.js apps, Angular dashboards, CI pipelines that bill by the minute — I can tell you: &lt;strong&gt;npm is holding you back&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>