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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ideadesignmedia/config.js

v1.0.3

Published

Side-effect-only helper that reads a `config.json` file in your current working directory and copies its contents into `process.env`.

Readme

@ideadesignmedia/config.js

Side-effect-only helper that reads a config.json file in your current working directory and copies its contents into process.env.

Installation

npm install @ideadesignmedia/config.js

Prepare config.json

Create a config.json alongside the script that will run your application. Two shapes are supported:

  • Object form

    {
      "API_BASE_URL": "https://api.example.com",
      "NODE_ENV": "development"
    }
  • Array form

    [
      { "key": "API_BASE_URL", "value": "https://api.example.com" },
      { "key": "NODE_ENV", "value": "development" }
    ]

Every key becomes an environment variable (values are stored as strings). Missing files cause the package to throw Error: Please add config.json on startup.

Usage

Import the package once near your entry point. No value is exported; the import is only for its side effects.

  • CommonJS

    require('@ideadesignmedia/config.js');
    
    console.log(process.env.API_BASE_URL);
  • ES modules / TypeScript

    import '@ideadesignmedia/config.js';
    
    const apiBaseUrl = process.env.API_BASE_URL;

The module can be imported multiple times without issue. Subsequent imports simply reuse the environment variables already attached to process.env.

Tips

  • Keep config.json out of version control if it contains secrets; add it to .gitignore.
  • Prefer string values in your config file; Node.js stores environment variables as strings.
  • Combine this loader with packages like dotenv or deployment-specific configuration files as needed.