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

@velsa/ts-env

v1.0.3

Published

Strongly typed environment variables for Typescript projects

Downloads

7

Readme

Typescript ENV

Bring strongly typed environment variables into your Typescript project :)

Install

npm install @velsa/ts-env

Usage / Examples

import env from '@velsa/ts-env'

export const myenv = {
    // Strings are the default type
    API_TOKEN: env("API_TOKEN"),
    // API_TOKEN type: string

    // Inferring types using the 'default' option
    SERVER_PORT: env("SERVER_PORT", { default: 3000 })
    // SERVER_PORT type: number

    // You can set boolean env vars like that: ENABLE_AUTH=yes
    ENABLE_AUTH: env("ENABLE_AUTH", { default: false })
    // ENABLE_AUTH type: boolean

    // Strict typings and autocomplete using the 'allowed' option
    NODE_ENV: env("NODE_ENV", { allowed: ["dev", "prod", "test"] as const }),
    // NODE_ENV type: "dev" | "prod" | "test"
    // cool, right? 😎
}

Features

The library exposes only one method, which accepts the var name and some options:

env(varName: string, 
    options?: { 
        default?: string | number | boolean,
        allowed?: string[] | number[]
    }
)

The env() function reads the varName value from the environment (process.env), converts it to the correct type, uses default if needed, checks the value against allowed values if they are provided and generates TS type and type checks on the fly.

Boolean env vars can be set to "true" or "yes" for true values and anything else for false.

If no default or allowed values are provided, the return type is string.

If default value is not provided and env var is not found, the function will throw an error.

If allowed array is provided and the env var value is not in the allowed list, the function will throw an error.