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

npmrcd

v1.0.3

Published

CLI that installs a daemon/agent that will automatically switch between npm registries on a developer machine.

Downloads

7

Readme

npmrcd

About

Since I frequently change between working from home, on the road, and the office I wanted to make sure I was using the private registry when connected to our corporate networks.

This is daemon that watches for, and automatically switch between private/work and public/default npm registries based on the availability of the private registry.

If the private registry can be resolved via DNS this daemon will switch your .npmrc file using the npmrc in the background. This is a basic detection mechanism, and could be modified to have more complex triggers if necessary.

Requirements

  • Node.js 10+
  • npm 6+
  • macOS (PRs adding Linux daemon setups are very welcome)

Install

npm install -g npmrcd

Setup

Run the setup command after installing. The registry parameter is required.

# Install and setup the daemon with a cafile for the registry
npmrcd setup \
 --cafile="https://certs.acme.com/ACME-Root-CA.crt" \
 --registry="https://eng.acme.com/nexus/repository/registry.npmjs.org"

Daemon Setup Options

The cafile parameter is optional and only required if access to the given registry requires a CA Certificate file.

A triggerssid parameter is also supported to specify WiFi networks where the daemon should switch to the private registry even if it's not accessible. This is useful if the registry should be used in conjunction with a VPN on specific networks.

For example, the following setup would switch to the eng.acme.com registry if the address can be resolved using DNS or the machine is connected to one of the listed SSIDs.

npmrcd setup \
 --triggerssid="Acme Guest Wifi" \
 --triggerssid="Acme Customer Wifi" \
 --cafile="https://certs.acme.com/ACME-Root-CA.crt" \
 --registry="https://eng.acme.com/nexus/repository/registry.npmjs.org"

The registry and cafile options are explained in detail in the npm-config docs.

Uninstall

# Remove the daemon
npmrcd remove
npm uninstall -g npmrcd

Daemon Logs

macOS & Linux

  • Logs are stored in /tmp/npmrcd.stdout and /tmp/npmrcd.stderr.
  • Configuration files are stored in ~/.npmrcd and ~/.npmrcs.