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

@ez-hex/config

v1.0.2

Published

Load Config from any place and merge it into one.

Downloads

4

Readme

@ez-hex/config

Load Config from any place and merge it into one.

Install

npm install --save @ez-hex/config
# or
yarn add @ez-hex/config

Usage

Base

interface MyConfig {
    // defined your config struct
    keyA: string
    keyB: number
    keyC: boolean
}
// config is Partial<MyConfig>
const config = loadConfig<MyConfig>(defaultLoader({
    keyA: 'default A',
    keyC: false,
}), jsonLoader('./simple.json'), envLoader('AAA_'))

// config is MyConfig
const config = loadConfigWithDefault<MyConfig>({
    keyA: 'default A',
    keyB: 1,
    keyC: false,
}, jsonLoader('./simple.json'), envLoader('AAA_'))

Implement Your Own Loader

There are two type: SyncLoader and AsyncLoader

type Loader<T> = SyncLoader<T> | AsyncLoader<T>
type SyncLoader<T> = () => Partial<T>
type AsyncLoader<T> = () => Promise<Partial<T>>

If all args of loadConfig or loadConfigWithDefault is SyncLoader, then return the value directly, else your will get a Promise.

function load_with_async_fs<T>(path: string): () => Promise<T> {
    return () => {
        return new Promise<T>((resolve, reject) => {
            readFile(path, 'utf-8', (err, data) => {
                try {
                    resolve(JSON.parse(data))
                } catch (err) {
                    reject(err)
                }
            })
        })
    }
}

// config is Promise<Partial<T>>
const config = loadConfig<Config>(jsonLoader('./simple.json'), envLoader('AAA_'), load_with_async_fs<Config>('./aaa'))

// config2 is Promise<T>
const config2 = loadConfigWithDefault<MyConfig>({
    keyA: 'default A',
    keyB: 1,
    keyC: false,
}, jsonLoader('./simple.json'), envLoader('AAA_'), load_with_async_fs<Config>('./aaa'))

Loaders

defaultLoader

SyncLoader

It just return the argument

envLoaderr

SyncLoader

It will load all env which has special prefix and parse the value with JSON.parse

// env.js
const result = envLoaderr('A_')()
console.log(result)
A_KEYA=aaa node env.js
# {KEYA: "aaa"}

jsonLoaderr

SyncLoader

load the file and parse the content with JSON.parse