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

oniyi-config

v1.1.2

Published

Simple config file loader

Downloads

14

Readme

oniyi-config NPM version Dependency Status

Simple config file loader

Installation

$ npm install --save oniyi-config

Usage

const oniyiConfig = require('oniyi-config');

const cfg = oniyiConfig({
  sourceDir: __dirname,
  baseName: 'providers',
  environment: 'production',
  });

will merge jsand json files starting with name providers in __dirname iteratively. File name schema is providers.[environment].(json|js).

environment is optional and defaults to development. Possible values are anything you can set in process.env.NODE_ENV. For file name resolution, process.env.NODE_ENV will be transformed to lower-case.

One special environment is local. It will always be loaded last. You can provide the same file name with different extensions. json will always be loaded before js, meaning js will overwrite json

Sample load order:

  1. providers.json
  2. providers.js
  3. providers.development.json
  4. providers.development.js
  5. providers.local.json
  6. providers.local.js

Options

  • sourceDir, baseDir, basePath: single directory path to load config files from
  • sourceDirs: array of directory paths to load config files from. Files are loaded in preceding order (meaning the last one is loaded first extended with _.mergeWith() in reverse order; as customizer for _.mergeWith(), a custom function from lib/utils.js is used)
  • baseName: the baseName for config files (e.g. providers from the example above)
  • env, environment: the environment part of config file names (e.g. development from the example above) Note: local is always added / loaded

License

MIT © Benjamin Kroeger