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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@commit-generator/config

v1.0.1

Published

A configuration management utility.

Readme

@commit-generator/config

This package provides a flexible and extensible configuration management utility for the Commit Generator project. It supports multiple configuration sources, including files, environment variables, and command-line arguments.

Installation

To use the configuration management utility in your project, install the package as a dependency:

pnpm install @commit-generator/config

Usage

  1. Define Configuration Sources
    First, define where the configuration values should be loaded from. The example below sets up three sources:
  • File (.myConfigFile.json): Stores persistent configurations.
  • Environment variables (MY_PREFIX_*): Loads configurations from environment variables.
  • Command-line arguments (--key=value): Allows overriding configurations via CLI.`
import createConfigManager, {
  IConfigDefinitions,
  IConfigSource,
} from '@commit-generator/config';

const sources: Array<IConfigSource> = [
  { name: 'local', type: 'file', path: '.myConfigFile.json' },
  { name: 'env', type: 'env', prefix: 'MY_PREFIX' },
  { name: 'arg', type: 'arg' },
];

export type IConfigType = {
  provider: string;
};

const configDefinitions: IConfigDefinitions<IConfigType> = {
  type: 'object',
  properties: {
    provider: { type: 'string' },
  },
  required: ['provider'],
  additionalProperties: false,
};

const configManager = createConfigManager({
  sources,
  definitions: configDefinitions,
});

export default configManager;
  1. Load Configuration
    Once the sources are defined, you can load the configuration dynamically:
import configManager from 'path/to/myConfigManager';

const config = await configManager.loadConfig();

console.log(config);
  1. Set a Configuration Value
    You can modify a configuration setting and store it in a specific source (e.g., local file):
import configManager from 'path/to/myConfigManager';

await configManager.set('provider', 'some_provider', 'local');
  1. Unset a Configuration Value
    To remove a configuration key from a specific source:
import configManager from 'path/to/myConfigManager';

await configManager.unset('provider', 'local');

License

This package is licensed under the MIT License.