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

@notiv/env-config

v1.0.0

Published

Loads global configurations for client and server from root directory

Downloads

2

Readme

@dicehub/config-env-loader

npm version

Load configuration files based on NODE_ENV variable

Install

npm install @dicehub/config-env-loader -S

# via yarn
yarn add @dicehub/config-env-loader

Usage

Set NODE_ENV

Only the file that corresponds to the NODE_ENV variable will be included

$ export NODE_ENV=development

Create configuration file config/development.yaml:

# <root>/config/development.yaml

TEST_VAR: 20

Include the plugin in your entry file

// <root>/index.js

require('@dicehub/config-env-loader')({
  // Config directory
  configPath: './config/',
});

And now, every variable that is in the file config/development.yaml is available through the process.env

console.log(process.env.DEVELOPMENT_ENV_VAR) // '42';

The value is string because https://nodejs.org/dist/latest-v10.x/docs/api/process.html#process_process_env

Options:

var conf = require('@dicehub/config-env-loader')({
  // The directory where the configuration files for the NODE_ENV are located
  configPath: './config/',

  // The array of files to be included, not depending on the NODE_ENV
  include: ['./common-config.yaml']
});

// The variable conf contains all that is included
// Except that the types are not converted
process.env.TEST_VAR // '42'
conf.TEST_VAR // 42

Default config file

  1. By default, if NODE_ENV is not provided, the configuration development.yaml is loaded
  2. if in config folder there is a file general.yaml then it will be loaded before the {NODE_ENV}.yaml