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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@entwico/node-config

v1.3.1

Published

An opinionated implementation of node server configuration.

Readme

@entwico/node-config

An opinionated implementation of node server configuration.

Installation

npm i @entwico/node-config

Usage

Config definition

First, describe a config container:

class SubSub {
  @Property() prop: string;
}

class Sub {
  @Property() sub: SubSub;
  @Property() prop: string;
}

class Config {
  @Property() sub: Sub;
  @Property() prop1: string;
  @Property() prop2: number;
  @Property() prop3: boolean;
  @List(String) strings: string[];
  @List(SubSub) subsubs: SubSub[];
}

Config files

You can pass multiple config files:

const conf = loadConfig(Config, { env: { prefix: 'APP_' }, files: ['config.yaml'] });

The files will override each other's settings (the later the file is in the list, the more priority it will have).

Following file formats supported:

  • .yml / .yaml
  • .js
  • .json

Example file:

sub:
  sub:
    prop: test
  prop: test
prop1: test
prop2: 123
prop3: false
strings:
  - test1
  - test2
subsubs:
  - prop: test

Environment variables

const conf = loadConfig(Config, { env: { prefix: 'APP_' }, files: paths });

The environment variables take precedence over the files' settings.

Examples:

export APP_SUB_PROP=test # sets conf.sub.prop = 'test'
export APP_STRINGS__0=test # sets conf.strings[0] = 'test'
export APP_SUBSUBS__1__PROP=test # sets conf.subsubs[0].prop = 'test'

License

MIT