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

packagerc

v1.1.0

Published

Extended rc parser which extracts rc app name and defaults from package.json

Downloads

33

Readme

packagerc

Extended rc parser which extracts rc app name and defaults from package.json

USAGE

The API is the same as rc, except the first argument -- the appname string -- is also optional. If not provided, it will be extracted from the relevant package.json, relative to process.cwd().

// package.json
{
  "name": "some-package",
  // ...
  "rc": {
    "name": "somepackage"
  }
}

The packagerc lib allows you to invoke rc with the appname of "somepackage" from anywhere within your app, optionally supplying defaults just like for rc:

var conf = require('packagerc')({
  // user-specified defaults
  port: 2468
})
conf.port === 2468

Config resolution is exactly the same as rc:

// .somepackagerc
{
  "port": 8888
}

var conf = require('packagerc')({
  port: 2468
})
conf.port === 8888

Defaults may also be provided within the package.json, which will be overridden by any defaults you provide explicitly as part of the call to rc.

// package.json
{
  "name": "some-package",
  // ...
  "rc": {
    "name": "somepackage",
    "defaults": {
      // package-specified defaults
      "port": 4444,
      "host": "0.0.0.0"
    }
  }
}

var conf = require('packagerc')()
conf.port === 4444
conf.host === '0.0.0.0'

var conf = require('packagerc')({
  port: 2468
})
conf.port === 2468
conf.host === '0.0.0.0'