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-update-check

v1.0.1

Published

Env update check package provides checking system for environment variables, that ensures that you never forget to change environment variable again when you're deploying your application.

Downloads

3

Readme

What is env-update-check

Env update check package provides checking system for environment variables, that ensures that you never forget to change environment variable again when you're deploying your application.

How does it work?

Create .env.check file with variable names you want to check and their status as it's displayed below:

TEST_VARIABLE_1=unchanged
TEST_VARIABLE_2=unchanged

Setup env-update-check to run in your CI script.

Then each time you change variable value or add a new variable, change it's value to changed like below:

TEST_VARIABLE_1=changed
TEST_VARIABLE_2=unchanged
NEW_TEST_VARIABLE_3=changed

After your new code changes get to your staging or main branch, your build will fail until you both change the variable in your environment and then in .env.check file.

unchanged == no change
changed == changed - will error out on staging and prod
staging-changed == changed on staging - will error out on prod only 

Now commit your changes and enjoy (hopefully) smooth deployments. ⛵️

Currently production check is avaliable only when your production branch is named main. Tested only on Gitlab CI