npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@shilong/nrm

v0.2.0

Published

NPM registry manager. include: yarn, taobao, tencent

Downloads

2

Readme

@shilong/nrm

This is a simple npm registry manager cli tool.

min package size downloads vulnerabilities

Install

$ npm i @shilong/nrm -g

## check if install successful
$ slnrm --help

Usage

# show available registry
$ slnrm ls
   * npm         https://registry.npmjs.org/
     yarn        https://registry.yarnpkg.com/
     taobao      https://registry.npmmirror.com/
     tencent     https://mirrors.cloud.tencent.com/npm/
# use one registry
$ slnrm use taobao
     npm         https://registry.npmjs.org/
     yarn        https://registry.yarnpkg.com/
   * taobao      https://registry.npmmirror.com/
     tencent     https://mirrors.cloud.tencent.com/npm/

Difference


# install with npm registry

$ npm i --verbose
...
npm http fetch GET 200 https://registry.npmjs.org/@types%2fnode 3665ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@types%2freact 559ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@types%2freact-dom 377ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/eslint 775ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/eslint-config-next 1183ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/typescript 3514ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/next 4558ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/@opentelemetry%2fapi 314ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/fibers 281ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/node-sass 324ms (cache miss)
npm http fetch GET 200 https://registry.npmjs.org/react 1057ms (cache miss)
...

# install with taobao registry

$ npm i --verbose
...
npm http fetch GET 200 https://registry.npmmirror.com/@types%2fnode 444ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/@types%2freact 125ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/@types%2freact-dom 77ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/eslint 109ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/eslint-config-next 376ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/typescript 462ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/next 520ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/@opentelemetry%2fapi 54ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/fibers 42ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/node-sass 42ms (cache miss)
npm http fetch GET 200 https://registry.npmmirror.com/react 270ms (cache miss)
...