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

envpm

v1.2.1

Published

npm registry environment manager

Downloads

27

Readme

envpm

Build Status npm install npm version js-standard-style License

easy directory-level configuration scoping for npm

example

installation

npm install -g envpm

usage

envpm proxies commands to npm, but (in the event of a .npmrc file in your current working directory or any directory up from that) uses the configuration information present in that file.

The only command provided by envpm is which, used as such:

envpm which

This will print the location to the .npmrc that envpm will source if run from your current working directory.

If you'd like to make npm dir aware all the time, put the following command in your .bashrc:

alias npm=envnpm

Important: Be sure to set a different cache directory in your overridden .npmrc so that your private cache doesn't interfere with your public cache (and vice versa). Here's an example (minimal) .npmrc:

registry=http://your.registry/
cache=/full/path/to/.local-cache

as a module

var envpm = require('envpm')

envpm(dir, args) // executes npm with args,
                 // looking for .npmrc file starting in dir

license

MIT