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

@pioryd/type-config-with-env

v1.1.6

Published

Typed nested config that can be overwritten by environment variables

Downloads

11

Readme

@pioryd/type-config-with-env

main branch - test and build

Installation

# npm
npm install @pioryd/type-config-with-env
# yarn
yarn add @pioryd/type-config-with-env

Introduction

Typed nested config that can be overwritten by environment variables.

!!! Important

You must load environment variables on Your. For example: dotenv or cross-env

Note: dotenv must be runned before all other imports

Example usage

Source example

or bellow:

Config files (.ts or .env)

userConfig.ts

import { UserConfig } from "./src/lib/types";

export const userConfig: UserConfig = {
  email: "[email protected]",
  password: "myPassword",
  days: {
    numbers: "1, 2, 3, 4", // will be converter to number[]
  },
  nodeEnv: {
    production: {
      password: "productionPassword",
    },
    test: {
      password: "testPassword",
    },
  },
};

.env (override userConfig.ts)

  • [conf_] - prefix

  • [days_numbers] - flatten userConfig key

conf_days_numbers="7, 8, 9"

.gitignore

.env
userConfig.ts

Sources files

src/lib/types.ts

import { NodeEnvModes } from "@pioryd/type-config-with-env";

export interface UserConfig {
  email: string;
  password: string;
  days: {
    numbers: string;
  };
  // required - more info bellow "Build modes"
  nodeEnv?: NodeEnvModes<UserConfig>;
}

export interface FullConfig extends Omit<UserConfig, "nodeEnv" | "days"> {
  url: string;

  // replacing UserConfig["days"]
  days: {
    numbers: number[];
  };
}

src/lib/config.ts

import { mergeUserConfigWithEnv } from "@pioryd/type-config-with-env";

import { userConfig } from "../../userConfig";
import { FullConfig } from "./types";

const userConfigWithEnv = mergeUserConfigWithEnv({
  userConfig,
  options: { preText: "conf_", delimiter: "_" },
});

export const config: FullConfig = {
  ...userConfigWithEnv,
  url: `localhost?email=${userConfigWithEnv.email}&pass=${userConfigWithEnv.password}`,
  days: {
    numbers: userConfigWithEnv.days.numbers.split(",").map(Number) || [],
  },
};

Usage in project

Use anywhere in app, for example:

src/index.ts

// dotenv must be loaded as first
import dotenv from "dotenv";

//
import { config } from "./lib/config";

dotenv.config({ path: ".env", override: true });

console.log(config);

/**
 * OUTPUT:
 * {
 *   // from userConfig.ts
 *   email: '[email protected]',
 *   // from userConfig.ts - overridden by production
 *   password: 'myPassword',
 *
 *   // from .env parsed inside FullConfig
 *   days: { numbers: [ 7, 8, 9 ] },
 *
 *   //  created in  inside FullConfig
 *   url: '[email protected]&pass=productionPassword'
 * }
 */

Build modes (development, production, etc.)

userConfig.ts

import { UserConfig } from "./src/lib/types";

export const userConfig: UserConfig = {
  email: "[email protected]",
  password: "myPassword",
  days: {
    numbers: "1, 2, 3, 4", // will be converter to number[]
  },

  // build modes
  nodeEnv: {
    production: {
      password: "productionPassword",
    },
    test: {
      password: "testPassword",
    },
  },
};