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

env-emitter

v1.0.0

Published

Adds event emitters to process.env

Downloads

4

Readme

env-emitter

Node.js module that adds event emitters to process.env. Requires no dependencies.

Installation

npm install env-emitter

Include the module at top of main file. This is only needed once in the application because it replaces the global process.env.

import 'env-emitter'

Usage

Listen for get events

import 'env-emitter'

process.env.on('get', event => {
    console.log(`Variable ${event.name} used at ${event.caller}`)
})

const test = process.env.FOO_BAR

// outputs: FOO_BAR used at /app/directory/file.js:7:13

event properties available:

  • event.name
    • Name of variable accessed, such as NODE_ENV
  • event.value
    • Value of variable accessed (or undefined)
  • event.caller
    • String of where accessed, such as /app/directory/file.js:7:13
  • event.callerIsCoreNode
    • Boolean, true if variable was accessed from a core Node module. This is helpful for filtering. Example being console.log() access lots of environment variables.

Listen for set events

import 'env-emitter'

process.env.on('set', event => {
    console.log(`Variable ${event.name} changed to ${event.newValue} at ${event.caller}`)
})

process.env.FOO_BAR = 'baz'

// outputs: FOO_BAR changed to baz at /app/directory/file.js:7:13

event properties available:

  • event.name
    • Name of variable being changed, such as NODE_ENV
  • event.caller
    • String of where variable is being changed, such as /app/directory/file.js:7:13
  • event.previousValue
    • Value of variable BEFORE change (current value)
  • event.newValue
    • Value of variable AFTER change (value after any listeners complete)

More examples

Prevent any changes to process.env

process.env.on('set', event => {
    throw new Error('Setting environment variables is not allowed')
})

Log warning for undefined vars

process.env.on('get', event => {
    // skip internal Node usage
    if (event.callerIsCoreNode) {
        return
    }   

    if (event.value === undefined) {
        console.log(`⚠️ ${event.name} at ${event.caller}`)
    }
})