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 🙏

© 2025 – Pkg Stats / Ryan Hefner

azure-env-safe

v1.0.0-beta.4

Published

dotenv-safe for azure functions

Readme

Azure-Env-Safe

A zero-dependency lightweight environment variable checker for azure functions written in Javascript/Typescript.

Installation

npm install --save azure-env-safe

Why

Inspired by dotenv-safe, it's a good practice to keep your config separate from your application. It is also a good practice to fail early and with good error messages to help debugging. This approach will help you avoid having random error messages from appearing because an environment variable is missing and only finding it at runtime once your application is deployed. dotenv-safe requires a .env.example file, so if you were to use it with an azure function, then you would have both a local.settings.example.json and a .env.example where your env variables could go. Rather than having a confusing situation like that with 2 example files, this repo just uses your local.settings.example.json file the same way that dotenv-safe works.

How

This package will find your application's local.settings.example.json and verify that the environment variables in your app. If any environment variables are missing, a descriptive error will be thrown telling you which environment variables are missing.

Usage

Let's say you have a project like this

my-func/index.js
local.settings.json
local.settings.example.json

In my-func/index.js add this code to the very top of the file:

require('azure-env-safe/config');

This will find the the local.settings.example.json in your project and assert that the environment variables exist.

Config

You can pass additional options to configure this library.

require('azure-env-safe').config({
    example: './.my-env-example-filename.json'
});

example

Default: local.settings.example.json.

Path to the example json file.