<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>sigh.dev - Scott Cooper&apos;s dev blog - #npm</title><description>sigh.dev is Scott Cooper&apos;s dev blog about TypeScript, React, San Francisco, and the web. - Posts tagged with &quot;npm&quot;</description><link>https://sigh.dev/</link><item><title>My Favorite NPM Command</title><link>https://sigh.dev/posts/favorite-npm-command/</link><guid isPermaLink="true">https://sigh.dev/posts/favorite-npm-command/</guid><description>An ode to `npm repo`, the best npm command.</description><pubDate>Sat, 11 Oct 2025 08:00:00 GMT</pubDate><content:encoded> 
&lt;p&gt;Let’s talk about my favorite npm command, &lt;code&gt;npm repo&lt;/code&gt;.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Open package repository page in the browser - &lt;a href=&quot;https://docs.npmjs.com/cli/v11/commands/npm-repo&quot; target=&quot;_blank&quot;&gt;npm docs&lt;/a&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;This command is dead simple. Open the repository page for the given package in the browser. If you omit the package name, it will look at the local package.json and open that repository.&lt;/p&gt;
&lt;p&gt;I use this command several times a day—often hourly. What’s great is that it works for published npm packages and any repo with a &lt;code&gt;package.json&lt;/code&gt;. I’ll use it just to open the repo I’m working in, too. I don’t need a bunch of bookmarks or to hope that my current repo shows up on the GitHub homepage. I’ll just run &lt;code&gt;npm repo&lt;/code&gt; and dig into any package, and I’ve yet to be rickrolled. Googling certain packages is annoying because you often have to add “GitHub repo” to the search.&lt;/p&gt;
&lt;h2&gt;&lt;a href=&quot;#history&quot;&gt;History&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The npm repo command was added in 2013 in commit &lt;a href=&quot;https://github.com/npm/npm/commit/0223389130dfd220d2a18dfe7058c4f7f0b14808&quot; target=&quot;_blank&quot;&gt;0223389&lt;/a&gt; by &lt;a href=&quot;https://github.com/tj&quot; target=&quot;_blank&quot;&gt;TJ Holowaychuk&lt;/a&gt;, creator of Express, Mocha, and other popular npm packages. Ignoring various issues opened on the CLI, this is the only contribution he made directly.&lt;/p&gt;
&lt;h2&gt;&lt;a href=&quot;#other-package-managers&quot;&gt;Other package managers&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The yarn cli does not have a repo command. Pnpm does not have a repo command, instead &lt;a href=&quot;https://github.com/pnpm/pnpm/blob/1b15e45ae949485ba9b9bfd4e079b551ab7d8819/pnpm/src/pnpm.ts#L30&quot; target=&quot;_blank&quot;&gt;they forward the command to the npm cli&lt;/a&gt; among a list of other commands they forward. &lt;code&gt;pnpm home&lt;/code&gt; is another good one they forward to npm, I just don’t usually reach for that one.&lt;/p&gt;
&lt;p&gt;As I move further away from using Koa, Express, and TJ’s other legacy projects, I’m positive I’ll keep using &lt;code&gt;npm repo&lt;/code&gt;. Praise TJ.&lt;/p&gt;</content:encoded><category>typescript</category><category>npm</category><category>tj</category></item></channel></rss>