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

@cley_faye/loadconfig

v4.1.0

Published

Load configuration from various places

Downloads

15

Readme

@cley_faye/loadconfig

Load configuration by looking into multiple places, updating values with each lookup:

  • default values
  • from a specific section in package.json
  • from a json file
  • from a js file
  • from command line flags

Configuration is very basic, and mostly handle strings, numbers, bool and array of those. Array values defined in later configuration source overrides completely values from previous sources. This mean that an array value set in a json file would be completely erased by a value set in a js file or on command line.

Usage

Where you need your configuration, call the function exported by the library.

import loadConfig from "@cley_faye/loadconfig";

loadConfig(
  {
    options,
    configName,
  },
).then(config => {});

The result is cached by default; that is because CLI arguments are removed from argv, so subsequent calls could return a different value than the first call.

Settings

Configuring options

Each value can be either a string, a number, a boolean, or an array of these. For array values, it means that the command line will accept multiple occurrence of the same argument. The options argument is an object where keys are configuration options names and values are objects that have the following properties:

  • cliName: optional name for reading from the command line (default to kebab case of the option name)
  • multiple: set to true to change the option type to be an array of values
  • type: expected value type. Only used for reading from CLI. Can be string, number or boolean. A special type object can be used; it will pass the content of the json/javascript config as-is, and cannot be used for CLI.
  • defaultValue: an optional default value

Naming the config source

The configName argument is the name to use when looking for configuration in package.json and in external files. It is used to find a property by that name in package.json, and for files names .<configName>.js and .<configName>.json.

It is possible to disable prefixing the config files by a dot (.) by adding the noDotFile property, set to true. It is also possible to skip some data source by setting the disableSource property.

From command line

Options can be read from command line. If an argument match, it is removed from the list of arguments. If the same argument is matched multiple time, only the latest one is kept, except for properties that are arrays, in which case each value is concatenated to the array. It is possible to remove a value using --no-<arg name>, except for booleans where it would set them to false.