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

@slytrunk/app-env

v3.2.2

Published

Import .env files per APP_ENV

Downloads

9

Readme

app-env

Import .env files per APP_ENV

Usage

module.exports = {
  plugins: [
    [
      "module:@slytrunk/app-env",
      {
        moduleName: "@slytrunk/app-env",
        cacheIdentifier: process.env.APP_ENV,
        envs: {
          stage: ".env.stage",
          production: ".env.production"
        }
      }
    ]
  ]
}

Then you can import env variables in your code:

import { API_URL } from "@slytrunk/app-env";

Be sure to specify APP_ENV up front.

$ APP_ENV=stage yarn dev

Debug Mode

If your APP_ENV is not production, we support hot-loading different environments so you can test multiple environments in one build.

import { setEnvironment } from "@slytrunk/app-env/debug";
setEnvironment("stage");

NOTE: It's a good idea to set cacheIdentifier as babel will cache the results of this module for subsequent builds and may get stuck in debug mode.

You can get a list of available environments so you can build ui to switch environments:

import { getEnvironmentOptions } from "@slytrunk/app-env/debug";

getEnvironmentOptions();
// ["stage", "production"]

Lastly, you can load variables directly from debug mode, however this is not recommended as the babel plugin does this for you automatically using the regular interface.

// !! Not Recommended
import { getEnv } from "@slytrunk/app-env/debug";

getEnv("API_URL");
// "http://api.example.com"

// Recommended
import { API_URL } from "@slytrunk/app-env";
// "http://api.example.com"