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

npmer

v1.0.1

Published

Deadly simple npmrc manager

Downloads

3

Readme

NPMER

Deadly simple npmrc manager

WHY npmrc MANAGER?

Don't ask me. Ask your self.

INSTALLATION

npm install -g npmer

USAGE

npmer [options]

Options:
  --list, -l     list npmrc  [boolean]
  --init, -i     init npmer  [boolean]
  --reset, -r    reset (remove) npmer  [boolean]
  --make, -m     create blank npmrc  [string]
  --del, -d      delete npmrc  [string]
  --use, -u      use npmrc  [string]
  --help, -h     Show help  [boolean]
  --version, -v  Show version number  [boolean]

HOW IT WORKS?

Simple, npmer --init creates $HOME/.npmer dir. Move your .npmrc file to $HOME/.npmer/original. Then, npmer creates this link:

`$HOME/.npmrc` -> `$HOME/.npmer/current` -> `$HOME/.npmer/original`

After that, any file that $HOME/.npmer/current is pointing will be your active .npmrc file.

CONFIGURATIONS?

Only two things can be configured:

  • .npmrc path which is taken from $NPM_CONFIG_USERCONFIG and fallback to $HOME/.npmrc if it's not set.
  • .npmer directory which is taken from NPMER_DIR and fallback to $HOME/.npmer if it's not set.

IMPORTANT

npmer --reset will remove everything inside $HOME/.npmer/original. Your original .npmrc file is stored in $HOME/.npmer/original. As long as it's name is original, everything should be safe. If not, anything with original as it's name will be taken to .npmrc. If there is no original in $HOME/.npmer, I don't know what will happen. But, I'm sure losing .npmrc file will not ruin your life or make you cry.

LICENSE

MIT