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

@eyal-poly/secret-config

v1.1.2

Published

Shared library package for Node.js for managing secrets in Google Secrets Manager

Readme

secret-config

A flexible and secure configuration management library for Node.js applications, designed to simplify environment variable handling and secret management in Google Secrets Manager

Features

  • 🔒 Secure environment variable validation
  • 🔑 Secret management with flexible configuration
  • 🌍 Environment-aware configuration loading
  • 📦 Easy integration with Google Cloud

Installation

npm install @eyal-poly/secret-config

Quick Start

const SecretConfig = require("./secretConfig");

async function initializeApp() {
  try {
    const config = new SecretConfig();

    config
      .addSecret("databaseUri", "DATABASE_URI")
      .addSecret("apiKey", "API_KEY");

    await config.initialize();

    const configuration = config.get();
    console.log(configuration.databaseUri);
  } catch (error) {
    console.error("Configuration initialization failed", error);
  }
}

Configuration Options

Environment Variables

The library supports the following environment variables:

| Variable | Description | Default | | ------------------------- | ------------------------------------ | ------------------ | | GOOGLE_CLOUD_PROJECT_ID | Required Google Cloud Project ID | None | | NODE_ENV | Application environment | development | | SECRET_CACHE_TTL | Secret caching time-to-live | 3600000 (1 hour) |

Custom Initialization

You can customize the configuration during initialization:

const config = new SecretConfig({
  projectId: "custom-project-id",
  environment: "staging",
  secretCacheTTL: 7200000, // 2 hours
});

Methods

  • addSecret(key, secretNamePostfix): Add a secret to be loaded
  • initialize(): Load secrets and prepare configuration
  • get(): Retrieve the loaded configuration

Error Handling

The library provides clear error messages for:

  • Missing required environment variables
  • Secret loading failures
  • Uninitialized configuration access

Security

  • Validates required environment variables
  • Supports secret caching
  • Designed for secure secret management

Compatible Environments

  • Node.js 18.x and above
  • Google Cloud
  • Various cloud and on-premises environments

Contributing

  1. Fork the repository
  2. Create your feature branch
  3. Commit your changes
  4. Push to the branch
  5. Create a Pull Request

License

[Your License - e.g., MIT]

Support

For issues, please file a GitHub issue in the repository.