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-state

v0.0.0

Published

Manage node.js app configs, with write-back and multiple configs per app

Downloads

1

Readme

config-state

NPM version

Manage node.js app configs in JSON with write-back and multiple configs per app.

Settings can also come from environment variables, but those settings are not written back to the config files.

import {loadConfig} from 'config-state'

const appName = 'run_count'

async function main () {
  const c = await loadConfig({appName})
  c.runCount = (c.runCount || 0) + 1
  await c.save()
  console.log(c)
}

main()

Simple use:

$ node example/run-count.js
{
  configLocation: '/home/sandro/.config/run_count/config-state/main.json',
  save: [AsyncFunction (anonymous)],
  runCount: 1
}
$ cat /home/sandro/.config/run_count/config-state/main.json
{
  "runCount": 1
}
$ node example/run-count.js
{
  runCount: 2,
  configLocation: '/home/sandro/.config/run_count/config-state/main.json',
  save: [AsyncFunction (anonymous)]
}
$ cat /home/sandro/.config/run_count/config-state/main.json
{
  "runCount": 2
}

Use an alternative config by name:

$ RUN_COUNT_CONFIG=beta node example/run-count.js
{
  config: 'beta',
  CONFIG: 'beta',
  configLocation: '/home/sandro/.config/run_count/config-state/beta.json',
  save: [AsyncFunction (anonymous)],
  runCount: 1
}
$ cat /home/sandro/.config/run_count/config-state/beta.json
{
  "runCount": 1
}
$ RUN_COUNT_CONFIG=beta node example/run-count.js
{
  runCount: 2,
  config: 'beta',
  CONFIG: 'beta',
  configLocation: '/home/sandro/.config/run_count/config-state/beta.json',
  save: [AsyncFunction (anonymous)]
}
$ cat /home/sandro/.config/run_count/config-state/beta.json
{
  "runCount": 2
}
$ 

Also

$ RUN_COUNT_CONFIG=some-file.json node example/run-count.js
{
  config: 'some-file.json',
  CONFIG: 'some-file.json',
  configLocation: 'some-file.json',
  save: [AsyncFunction (anonymous)],
  runCount: 1
}

Options

  • appName, the directory under .config we should be using. If you let it default to 'app', you better pick really good & distinct key names (or provide configName as a json file)

  • configName (env CONFIG), either the name of the config for this app we're using, or if it ends in ".json", the filename to *use. Defaults to 'main'.

  • initialConfig a json-able object to use when there's no existing config.