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

docker-config-loader

v1.0.0

Published

A really simple utility which loads the config from docker secrets if a specified env var is passed, if not it loads the config from a local path

Downloads

3

Readme

docker-config-loader

A extremely basic module to load a different config based on the environment.

Docs

Base Usage:

var loader = require('docker-config-loader');
var config;
try {
    config = loader({secretName:'prod_config.json',localPath:'./local_config.json'})
} catch(e) {
    //An Error occured, maybe the config was not found or could not be required.
}

If a environment var with the name set in secretName exists, the loader prefers it over the local path and tries to load it from /run/secrets/secretName ##Local Loading The Path is relative to node_modules. For Example: if you got a project structure as follows:

- node_modules
- config.json
- src
    - index.js

The loader will use the root path of the project, so if you want to require the config.json you would have to set the following options:

loader({secretName:'prod_config.json',localPath:'./config.json'})

I hope this module is a nice utility for very basic needs like mine.