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

ts-appconfig

v1.2.0

Published

Strongly Typed DotENV - Environment Variables

Downloads

69

Readme

ts-appconfig

ts-appconfig is a zero-dependency node module to get strongly-typed and IDE-friendly environment variables.

Environment variables are pulled from 3 places, in this order. This means that each step will be overwritten by the following step, if that step also contains the variable:

  1. Defaults from environment schema (your extended AppConfig class)
  2. .env file
  3. process.env

Install

npm i ts-appconfig

Setup

Create a file where you will declare your environment variable schema:

src/environment.ts

import { AppConfig, configure } from 'ts-appconfig';

export class Environment extends AppConfig {
	readonly APP_TITLE: string = '';
}

export const env: Environment = configure(Environment);

Create a .env file (and perhaps a .env.example file, too). Make sure you add .env to your .gitignore file, if it's not there already!

.env

APP_TITLE="Cool App"

Now import your env from the schema file you created and you're ready to use the environment variables!

src/index.ts

import { env } from './environment.ts';

console.log(env.APP_TITLE);

Output:

Cool App

Options

Pass ConfigurationOptions as a second argument to configure to customize how variables are loaded and parsed. All options are optional, you only have to specify the options you would like to change.

...
export const env: Environment = configure(Environment, {
	// Give the .env file your own name or file path
	//	Default: .env
	relativePath: 'my-own-filename.env',

	// Allow variables that are not in schema but are defined in .env
	//	Default: false
	allowUndeclared: false,

	// If true, fromProcessEnv will load .env variables from process.env
	//  Default: true
	fromProcessEnv: true,

	// Set process.env variables from the .env file
	//	Default: true
	overwriteProcessEnv: true,

	// Allow duplicate entries in the .env file for the same variable
	//	Default: false
	allowDuplicates: false,

	// Skip unknown/unparsable lines in the .env file, or throw an exception
	//	Default: false (throws exception)
	skipUnknownLines: false,
});