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

@moped/env

v0.1.5

Published

This module helps normalise your environment variables. It is part of the moped suite of utilities for creating composable configs for building node.js and react apps.

Downloads

28

Readme

env

This module helps normalise your environment variables. It is part of the moped suite of utilities for creating composable configs for building node.js and react apps.

You must load env before all other modules.

Installation

yarn add --dev @moped/env

Usage ES6

If you want your users to specify NODE_ENV manually:

import '@moped/env/auto';
import * as webpack from 'webpack;

In your build file:

import '@moped/env/production';
import * as webpack from 'webpack;

In your tests:

import '@moped/env/test';
import * as webpack from 'webpack;

In development:

import '@moped/env/development';
import * as webpack from 'webpack;

Usage ES5

If you want your users to specify NODE_ENV manually:

require('@moped/env/auto');
const webpack = require('webpack');

In your build file:

require('@moped/env/production');
const webpack = require('webpack');

In your tests:

require('@moped/env/test');
const webpack = require('webpack');

In development:

require('@moped/env/development');
const webpack = require('webpack');

Configuration

Once you are using @moped/env, you can configure your environment using .env files. You should make sure the following is included in your .gitignore file:

.env.local
.env.development.local
.env.test.local
.env.production.local

When reading an environment variable, @moped/env will first look in the actual environment, then .env.{NODE_ENV}.local, then .env.{NODE_ENV}, then .env.local then .env. You use .env for config shared amongst all environments/for setting up a default config. You can use the .local variants for confidential configuration that you don't want published to GitHub, and you can use the {NODE_ENV} variants to override config in different environments.

You should always try to ensure your app at least runs with no .local config, as this will make it easier to onboard new team members.

LICENSE

MIT