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

lively-config

v1.0.3

Published

## Usage ```js var path = require("path"); var LivelyConfig = require("lively-config").LivelyConfig

Downloads

6

Readme

lively-config

Usage

var path = require("path");
var LivelyConfig = require("lively-config").LivelyConfig

var liveConfig = new LivelyConfig();
/*
Order matters
liveConfig.using(... Highest Resolution Priority ...)
          .using(... Lower Resolution Priority ...)
          ...
          .using(... Lowest Resolution Priority ...)
          .finalize()
*/
liveConfig
  .usingEnvironmentVars()
  .usingFile(path.join(__dirname, "/test.json"))
  .usingHttp("http://ip.jsontest.com/", {}, 60000)
  .usingObject({"test":"config"})
  .finalize();

liveConfig.ready.then(() => {
  console.log(liveConfig.getNamedValue("name"))
  console.log(liveConfig.getNamedValue("ip"))
})

LivelyConfig Properties

ready

A promise created on construction that resolves after finalize has been invoked and all resolvers have resolved at least once.

LivelyConfig Methods

getNames()

Returns an Array of all the key names in LivelyConfig

getNamedValue(String name)

Returns the value of the given key name. If no value is found null will be returned

getMaybeNamedValue(String name)

Returns a wrapped value of the given key name. ({value: foundValue...}) If no value is found null will be returned

snapshot()

Returns a livelyConfig clone that contains a snapshot of all current configs.

usingEnvironmentVars(Optional interval)

Adds a EnvironmentVarsResolver with given config file to the LivelyConfig and will poll the environment vars if interval is given

usingFile(String filePath, Optional interval)

Adds a FileSystemResolver with given config file to the LivelyConfig and will poll the file if interval is given

usingHttp(String url, Object Headers, Optional interval)

Adds a HttpResolver and will call the url with headers and will poll the file if interval is given

usingObject(Object config, Optional interval)

Adds an ObjectResolver and use the provided config objects

finalize()

Locks the Resolvers list and will trigger the ready promise after all resolvers have resolved at least once

using(Resolver resolver)

Adds a resolver to the LivelyConfig

Resolver (abstract)

Resolvers are how configs are loaded into the LivelyConfig, out of the box there are 2 concrete implementations (FileSystemResolver and HttpResolver), you can make your own by inheriting from the Resolver Class provided and implementing a resolve method.