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

env-var-check

v0.0.8

Published

A simple CLI tool to check if all the required environment variables are set, based on a schema file.

Downloads

5

Readme

Environment Variables Checker

Description

It's a simple script to check if the environment variables are set and correspond to the expected values or types.

The types and/or values of the environment variables are defined in a schema. You can use it along Zod for validations or just with a Vanilla JS Object.

Usage

First, you need to initialize the checker with the schema and the environment variables.

npx env-var-check init

Or, if you want to use it with Zod:

npx env-var-check init --zod

This will generate a /env folder containing a schema.mjs file and a env.d.ts file to use with Typescript. (You will need to include the /env folder in your tsconfig.json file)

Then, you can run the checker:

npx env-var-check check 

Or your schema is using Zod:

npx env-var-check check --zod

You might want to add it to package.json and do something like this to check the environment variables before running the app:

{
  "scripts": {
    "predev": "env-var-check check",
    "prestart": "env-var-check check",
    "dev": "...",
    "start": "..."
  }
}

Options

init

  • --zod: Initialize the schema with Zod objects instead of Vanilla JS Objects

check

  • --zod: Use Zod to validate the environment variables
  • --env: Specify the path to the environment variables file (default: .env)
  • --schema: Specify the path to the schema file (default: ./env/schema.mjs)

TODO

  • [ ] Add tests
  • [ ] Add more options
  • [x] Implement the --schema option to specify a custom schema file path
  • [ ] Add more examples