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

config-captain

v2.0.5

Published

A dependency injectable configuration object

Downloads

5,620

Readme

README

Monorepo Build Continuous Deploy

Config Captain is designed to be a dependency injectable environment configuration object that can make helpful suggestions as to what configuration you have loaded.

import { Configuration } from "config-captain";

const config = new Configuration(
  { optionalVariable: "SOME_OPTIONAL_VARIABLE" },
  { requiredVariable: "SOME_REQUIRED_VARIABLE" },
  [{ SOME_OPTIONAL_VARIABLE: "VALUE_ONE", SOME_REQUIRED_VARIABLE: "VALUE_TWO" }]
);

config.getConfigurationVariable("requiredVariable");
config.getConfigurationVariableOrUndefined("optionalVariable");
config.getConfigurationVariables();

Variables

The keys in the optional and required variable section are the names you wish to use in code for your variables. The values should refer to the datasource location you wish to take a configuration value from.

{
  nameToReferToInCode: "name-in-datasource";
}

Optional Variables

const config = new Configuration(
  { someCanHaveVariable: "some-non-critical-variable" },
  {},
  [dataSource]
);

The first parameter to Configuration is optional variables. If these variables are not found in the datasource at startup time they will return undefined when you attempt to retrieve them.

Required Variables

const config = new Configuration(
  {},
  { someMustHaveVariable: "some-critical-variable" },
  [dataSource]
);

The second parameter to Configuration is required variables. If these variables are not found in the datasource at startup time, the Configuration will throw an error.

Datasources

This should be an array of key-value objects. If two or more datasources provide a value for a given variable, the earliest in the list will take priority. Process.env can be given as a datasource.

Accessors

getConfigurationVariables

Get the entire configuration object as a key-value object. The variables specified as 'optional' will be potentially undefined.

getConfigurationVariable

Get the value of a required environment variable. This will have the type of string.

getConfigurationVariableOrUndefined

Get the value of an optional environment variable. This will have the type of string | undefined.