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

secrets-manager-to-config

v1.0.41

Published

Pull secrets from secrets managers as nested json or yml file

Readme

secrets-manager-to-config

Table of Contents

Upload a ts-file as a Secret

ts-node upload.ts --secret_name <secret-name> --ts_path <ts-filepath>

This package aims at managing secrets saved in ts format, so that UAT, PROD etc environments can infer their type from DEV config.

Assume that we have the following env config written in ts file:

// config/test.ts

const someConfig: {
  hihi: string;
  ohMy: {
    value: string;
    someArray: string[];
  };
} = {
  hihi: "bye",
  ohMy: {
    value: "gosh",
    someArray: ["hihi", "hjaaaaaaa"],
  },
};

export default someConfig;

Then this default export can be uploaded to secrets manager via

ts-node upload.ts --secret_name some-test-config --ts_path config/test.ts

where upload.ts is defined by uploadConfig:

// upload.ts

import { SecretConfig, uploadConfig } from "secrets-manager-to-config";

const secretConfig: SecretConfig = {
  awsRegion: "ap-southeast-2",
};

uploadConfig(secretConfig);

Sample Result

We have the following in secret manager:

Download Secrets

ts-node download.ts --secret_name <secret-name> --format <format> --save_at <filepath>

Assume that in AWS secret manages we have defined a secret abc with a.b.c = "123", then create a file download.ts and write

// download.ts

import { downloadConfig, SecretConfig } from "secrets-manager-to-config";

const secretConfig: SecretConfig = {
  awsRegion: "ap-southeast-2",
};

downloadConfig(secretConfig);

now you can pull your secret by

ts-node download.ts --secret_name abc --format yml --save_at test.yml

Here the format is of type json | yml | flat_env. The above results in

  • In yml format:

    # test.yml
    
    a:
      b:
        c: "123"

    This is suitable for spring boot project where we use application.yml.

  • In json format:

    {
      "a": {
        "b": {
          "c": "123"
        }
      }
    }

    This is suitable for nodejs project where we use env-cmd -f .env.json to load env config.

  • In flat_env format:

    a.b.c="123"

    This is suitable for ordinary .env files or application.properties for spring boot project.