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

gardisto

v0.3.0

Published

Automatically check and verify that environment variables in a project are set

Downloads

64

Readme

gardisto

Automatically check and verify environment variables in your project.

Installation

npm install gardisto

Usage

To use the gardisto package, simply require it in your project and call the checkEnvVariables function, passing the root directory of your project as an argument.

import { checkEnvVariables } from 'gardisto';

checkEnvVariables({ debug: false }, './path/to/project/root');

The gardisto function will recursively traverse all TypeScript files in the specified directory and its subdirectories, checking for any references to process.env variables. If a variable is not set, it will log an error with the file name and line number where the variable is referenced. If a variable is set but empty, it will log a warning with the file name and line number. Additionally, if a variable is used with an OR operator (|| or ??), it will log a warning suggesting that the variable might not be set.

You can also specify include and exclude patterns to filter the files that are checked for environment variables. For example:

import { gardisto } from 'gardisto';

gardisto({
  debug: process.env.DEBUG === "true",
  include: ["src"],
  exclude: ["dist", "node_modules"],
}, './path/to/project/root');

This will only check files with the .ts or .tsx extension in the src directory and its subdirectories, excluding any files with the .test.ts or .spec.tsx extension.

Example

import { gardisto } from "gardisto";

gardisto({
  debug: process.env.DEBUG === "true",
  exclude: ["dist", "node_modules"],
});

// Output:
// Error: Environment variable DB_HOST is not set.
// File: ./src/db.ts
// Line: 10
// Warning: Environment variable API_KEY is empty.
// File: ./src/api.ts
// Line: 20
// Warning: Environment variable DB_USER has an OR operator. It might not be set.
// File: ./src/db.ts
// Line: 15

License

gardisto is licensed under the MIT License.