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

ceconfig

v1.0.7

Published

Comprehensive Easy Configuration

Downloads

3

Readme

Comprehensive Easy Configuration management

ceconfig makes it easy to get config values for your program -- both Node.js projects and Bash scripts. Just use it as shown below and get those values now. Worry about where they come from only if that complexity shows up on your project.

Usage in Node.js projects:

npm i -S ceconfig

Then, in your JavaScript:

const CONFIG  = require('ceconfig').mkCONFIG();

// ...

const editor = CONFIG('editor');

Usage in Bash scripts:

# Install ceconfig
npm i -g ceconfig

Then in your scripts:

EDITOR="$(ceconfig editor)"

# -or -

curl -sSL "http://$(ceconfig devserver):$(ceconfig devport)/my/favorite/route"

How

  • Looks everywhere for configuration data, in this order:
    • Commnad-line arguments.
    • Environment variables
    • All the expected spellings and types of .ceconfig.xyz files
    • All the expected locations for those .ceconfig files
    • Call your function to retrieve it