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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@cm-ayf/readenv

v1.2.0

Published

type-friendly utility for reading environment variable

Readme

@cm-ayf/readenv

type-friendly utility for reading environment variable.

Setup

npm install @cm-ayf/readenv

How to Use

This package exports one function: readenv:

// typescript
import readenv from 'readenv';

or

// javascript
const readenv = require('readenv');

readenv takes one argument, which specifies how you need to read environment variable. For example:

const env = readenv({
    TOKEN: {},
    NODE_ENV: {
        default: 'development'
    },
    apiKey: {
        from: 'API_KEY'
    }
});

Say you have dotenv.condig()ed with .env below:

# .env
TOKEN=token_keyboard_cat
API_KEY=api_key_keyboard_dog

then you will get:

const env = {
    TOKEN: 'token_keyboard_cat',
    NODE_ENV: 'development',
    apiKey: 'api_key_keyboard_dog'
}

Additionally, this env has static type like:

const env: {
    TOKEN: string;
    NODE_ENV: string;
    apiKey: string;
};

so that you can use it type-safe.

If an environment variable was missing with key that has no default value, it throws error. The error will tell you all environment variables that were missing.

API Document

readenv(options: { [key: string]: Option })

Input:

  • options: Object. The return object will inherit its keys. Each key can be configured with Option.

Returns: Object. Inherits keys from options. Each value will always be string.

Throws: Error object that tells us all environment variables missing.

Option

interface Option {
    default?: any;
    from?: string;
    parse?(src): any
}

Fields:

  • option.default
    • type: any
    • Default value for the key. readenv() never throws error about key with default.
  • option.from
    • type: string?
    • Environment variable name. Uses key if omitted.
  • option.parse
    • type: ((src: string) => any)?
    • Applied after environment variable was read before return. Returns string value if omitted.

Use Case

Examples are here;

twitter-v2

source code from twitter.ts.

works very well when new Twitter():

const env = readenv({
    consumer_key: { from: 'CONSUMER_KEY' },
    consumer_secret: { from: 'CONSUMER_SECRET' },
    access_token_key: { from: 'ACCESS_TOKEN_KEY' },
    access_token_secret: { from: 'ACCESS_TOKEN_SECRET' },
});

const twitter = new Twitter(env);