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

@uzelux/config

v1.1.0

Published

Configiguration loader and reader

Downloads

3

Readme

Config

A small configuration loader and reader.

Usage

Firstly, create a directory named Config at your project root

> cd YourAwsomeProject/
> mkdir Config
> cd Config/

Within Config, make a file index.js to act as our entry point, place the following sample config into it

module.exports = {
  App: {
    environment: process.env.APP_ENV || 'development',
    port: process.env.APP_PORT || 3000,
    secret: process.env.APP_SECRET || 'SuperSecret'
  }
}

You are all set! Just require the helper and get your config!

const Config = require('@uselux/config');
const env = Config.get('APP.environment');
console.log(env); // development

Methods

Config.get(path, default = null)

A basic getter that uses dot notation, will return default if the value in path is not set or unreachable due to any parent is undefined

Config.get('undefinedKey', 'defaultValue'); // defaultValue
Config.get('undefinedKey'); // null
Config.get('definedKey'); // defined value
Config.get('definedObjectKey') // object

Config.getOrFail(path)

Same as get(), but will throw an error if config is not defined

Config.getOrFail('undefinedKey'); // Error('Config is not defined')
Config.getOrFail('definedKey'); // defined value
Config.getOrFail('definedObjectKey') // object

Config.has(path)

Return a boolean based on the existence of the config

Config.has('undefinedKey'); // false
Config.has('definedKey'); // true

Config.hasOrFail(path)

Same as has(), but will throw an error if config is not defined, use this if you want to use try-catch instead of if-else

Config.hasOrFail('undefinedKey'); // Error('Config is not defined')
Config.has('definedKey'); // true

Recommendation