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

environment-var-checker

v1.0.3

Published

This library ensures required environment variables are defined at runtime. It will throw warnings or errors when key variables are missing or not correctly set.

Downloads

9

Readme

⚠️ Environment Variable Checker

📝 Description

A library that ensures required environment variables are defined at runtime. It will throw warnings or errors when key variables are missing or not correctly set.

This library is still in beta and hasn't been thoroughly tested with all Js frameworks/libraries. If you would like to contribute, writing tests, documentation, handling scenarios, please don't hesitate to raise PRs.

EB53D3C1-E84A-41C9-9168-17CC690BD25C 60AB8092-4F42-4103-AD3A-6A48157E8CC7

Getting Started

😐 Prerequisites

  • node >= 18
  • .env file setup in the project. Get a list of all required vars which will be used in the array as mentioned in the Usage section
# Sample .env for Vite
VITE_DB_HOST=localhost
VITE_DB_USER=root
VITE_DB_PASS=****

Installing

npm i environment-var-checker

🎬 Executing

Import and execute the library as shown below in a file that is the starting point of the application.

Examples:
  • index.js/App.js/index.html in React
  • main.ts in Angular
  • main.js/index.html in Vite, etc

Import

import { EnvChecker } from "environment-var-checker";

Usage

const requiredVars = ["VITE_DB_HOST", "VITE_DB_USER", "VITE_DB_PASS"];
const envChecker = new EnvChecker(requiredVars);
envChecker.check(); 

main.jsx - Vite

import { StrictMode } from "react";
import { createRoot } from "react-dom/client";
import App from "./App.jsx";
import "./index.css";
import { EnvChecker } from "environment-var-checker";

const requiredVars = ["VITE_DB_HOST", "VITE_DB_USER", "VITE_DB_PASS"];
const envChecker = new EnvChecker(requiredVars);
envChecker.check();

createRoot(document.getElementById("root")).render(
  <StrictMode>
    <App />
  </StrictMode>
);

😮‍💨 Common issues

🤓 Version History

  • 1.0.0
    • Initial Release
  • 1.0.3
    • Added console styling + QoL improvements