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

auto-config-updater

v1.1.0

Published

Things on internet move fast. New versions are being deployed all the time and it is hard to keep track of them. If you have hundreds of services running and some of them requires a specific version of an API you have to either put it in a config file, or

Downloads

7

Readme

Things on internet move fast. New versions are being deployed all the time and it is hard to keep track of them. If you have hundreds of services running and some of them requires a specific version of an API you have to either put it in a config file, or in the process ENV.

This is not optimal when new versions of your API provider are available weekly or monthly (ex: Facebook Marketing API) and that they retire the old version shortly after. How do you reliably change those versions without redeploying everything.

Well with this module you can now "listen" to changes in a remote file and act accordingly. No need to redeploy anything, just make sure to update your code to handle the changes. It can be in auth keys or versions or whatever you see fit.

installation

npm install --save auto-config-updater

usage

before you start

This module only currently supports JSON data. Upon being received the JSON object will be flattened:

//If you have this file
{
  "test": 123,
  "val": {
    "a": "value"
  }
}

//It will be converted to
{
  "test":123,
  "val.a": "value"
}

When you setup the handler you need to do it on the flat key (ex: if you want to get the a value when you need to enter val.a)

setting up a configuration

This module allows multiple variable files to be loaded.

Amazon S3

const CU = require("auto-config-updater")
const AWS = require("aws-sdk");
//setup your AWS SDK
AWS.config.update({...});

/**
 * @param {object}  s3_object AWS s3 object (new AWS.S3()).
 * @param {string}  bucket Name of S3 bucket.
 * @param {string}  key path to file in S3 bucket.
 * @param {integer} [refresh=60000] refresh time to look in ms.
 * @param {string}  [config='default'] name of the config
 */
CU.config.fromS3(new AWS.S3(), "mybucket", "mykey", 5000, "my-versions")

ElasticSearch

const CU = require("auto-config-updater")
const { Client } = require('@elastic/elasticsearch')
//setup your ElasticSearch client
const client = new Client({ node: '...:9200' });

/**
 * @param {object}  client ElasticSearch client.
 * @param {string}  index Index in ElasticSearch.
 * @param {string}  type Type in index.
 * @param {string}  id Id in index and type.
 * @param {integer} [refresh=60000] refresh time to look in ms.
 * @param {string}  [config='default'] name of the config
 */

CU.config.fromES(client, "index", "type", "id", 5000, "my-versions")

Value change handler

When a value has changed this handler will be triggered. You can add as many handlers as you want on each key

const CU = require("auto-config-updater")

/**
 * @param {string}    key Key to check on the value of the file.
 * @param {function}  handler Callback function for the handler.
 * @param {string}    [config='default'] name of the config
 */
CU.handler.onChange("key",handler, config)

CU.handler.onChange("version",(value, key) => {
  console.log("the value has changed:", value, key)
},"my-versions")