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

@roninjin10/typesafe-env

v0.0.1

Published

A light wrapper around zod for validating environment variables

Downloads

2

Readme

typesafe-env

Simple package for creating typesafe envs. It is a very light wrapper around zod

Getting started

  1. Install typesafe-env
npm i -D @roninjin10/typesafe-env
  1. Install peer dependencies if not already installed
npm i -D @roninjin10/typesafe-env
  1. Create a config for your env variables
const validators = {
  // Provide a description if you want to automatically generate documentation
  SERVICE_URI: z.string().url().describe('The URI to connect to ')

  HOST: z.string().default('localhost').describe(`HOST server should connect to
       Must be set to 0.0.0.0 in a docker container`),

  PORT: z
    .string()
    .transform((val) => Number.parseInt(val))
    .default('7300')
    .describe('PORT server should connect to'),
}
  1. Parse process.env (or any other object)
import { typesafeEnv } from '@roninjin10/typesafe-env'
export const env = typesafeEnv(validators, process.env)
env.PORT // type number
env.HOST // type string
// @ts-expect-error
env.NOT_ON_ENV

You now have an env object that will be 100% typesafe with autocompletion in your editor! This will defend against misconfigurations.

Automatically generate documentation

typesafe-env provides an easy way of turning your env validators into documentation

envSchema.ts

import { validators } from './env'
import { generateEnvDocs } from '@roninjin10/typesafe-env'

console.log(generateEnvDocs)

Then if you run ts-node envSchema you will get this printed to console

Environment Variables schema

SERVICE_URI
    The URI to connect to

HOST
    HOST server should connect to

PORT
    PORT server should ocnnect to

Contributing

All of @roninjin10 is open to contributions! To get started follow these steps

  1. Clone the repo
  2. Install pnpm npm install -g pnpm
  3. Install node modules pnpm install
  4. Cd to typesafe-env cd packages/typesafe-env
  5. Run the tests pnpm test
  6. Run the build pnpm build

Author: Will Cory 👨🏻‍💻