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

@punkish/zconfig

v1.0.4

Published

a zimple config utility

Downloads

4

Readme

zconfig

There are lots of wonderful utilities for storing and managing config information. This is not one of them. But, if you want a dependency-free utility, consider using this, a really zimple tool that works for me.

How To

Initialize a new config instance and access the settings as follows

import { Config } from './index.js';
const config = new Config().settings;
console.log(config)

See the accompanying example.js and the sample settings in config directory. The base setting in development.cjs (or default.cjs) is always read first. Then, depending on the process.env.NODE_ENV, the applicable test.cjs or production.cjs are deep-merged into the base settings. All the settings are available via the resulting config object.

process.env.NODE_ENV can be passed in via dotenv or by any other method setting the NODE_ENV environment variable. For example, by prefixing the call for your program as $ NODE_ENV=production node index.js

Important Notes:

  • the config directory has to be at the root of your application.
  • the settings have to use module.exports and have to have the .cjs suffix.