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

enve

v1.0.4

Published

JSON-parsed environment variables

Downloads

67

Readme

JSON-parsed environment variables. No dependencies. Parses string values in process.env with JSON.parse() to process.enve.

Used by illuminsight, Ptorx and other Xyfir projects.

npm version Build Status

Due to its simplicity, this project should not need frequent updates.

Usage

Let's assume you have an .env file with the following data:

STRING_VAR="Hello"
NUMBER_VAR=1234
BOOL_VAR=true
OBJECT_VAR={"foo":"bar"}
ALSO_STRING_VAR=Hello

Note that an .env file is completely irrelevant to how enve works. This is just an example. How you get the environment variables into your app is up to you.

Also note that the string variables may differ on how they handle quotes based on how your environment variables are passed to your app and how they're parsed before enve gets to them. Just remember, all enve does is pass the value to JSON.parse(), if that fails then it falls back to the original string value.

// Only needed in your entry file
import 'enve';
// or...
require('enve');

process.env.STRING_VAR === '"Hello"';
process.enve.STRING_VAR === 'Hello';

process.env.NUMBER_VAR === '1234';
process.enve.NUMBER_VAR === 1234;

process.env.BOOL_VAR === 'true';
process.enve.BOOL_VAR === true;

process.env.OBJECT_VAR === '{"foo":"bar"}';
process.enve.OBJECT_VAR.foo === 'bar';

process.env.ALSO_STRING_VAR === 'Hello';
process.enve.ALSO_STRING_VAR === 'Hello';

TypeScript

enve works fine with TypeScript.

import 'enve';

declare global {
  namespace NodeJS {
    interface Process {
      enve: {
        foo: string;
        bar: boolean;
        baz: {
          qux: number;
        };
      };
    }
  }
}