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

@zcong/viper

v0.1.5

Published

config loader for NodeJS

Downloads

4

Readme

node-viper

NPM version NPM downloads CircleCI codecov

config loader for NodeJS

Usage

const { Viper } = require('@zcong/viper')

const viper = new Viper({
  configName: 'config',
  configPaths: ['.'],
  configTypes: ['json']
})

console.log(viper.loadFiles())
console.log(viper.loadEnv())

config

interface RootConfig {
  configName?: string
  configPaths?: string[]
  configTypes?: supportTypes[]
  envPrefix?: string
}

RootConfig.configName

config file name without extension, eg: config, .env

RootConfig.configPaths

  • config file load paths, eg: ['.']

  • if start with $ will be replaced by env, eg: $HOME/test will be ~/test

RootConfig.configTypes

config file extensions, allowed is array of type supportTypes = 'json' | 'yaml' | 'toml' | 'dotenv', default is ['json', 'yaml', 'toml', 'dotenv']

RootConfig.envPrefix

if set, only load key of env whitch has this prefix. eg: set RootConfig.envPrefix = 'VIPER', only load VIPER_TEST, VIPER_FILE, TEST will be ignored.

VIPER_ or VIPER will be treated as VIPER_

Viper

Viper.loadFiles()

search config files by the order of configPaths and configTypes , will load the first finded and valid config file as return.

Viper.loadEnv()

load config from env.

you can call both of the two method, but the first will be merged by the second.

License

MIT © zcong1993