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

@lunarbyte/env-tool

v1.0.4

Published

Tools to validate, generate, and update env files

Downloads

350

Readme

Envtool

Installation

In your current project

npm install @lunarbyte/env-tool

Global install

npm install -g @lunarbyte/env-tool

Usage

Init

init will extract all the usages of process.env variables and create a schema file. The schema file is used for validating your .env file and syncing it with future changes.

# create a schema by scanning the example/ directory
env-tool init example/

Audit

List usages of process.env variables in your code. Does not write any files. Use this command to check for undocumented references to process.env variables. You might run this in your CI system to prevent merging code that introduces a new env variable without documenting it.

env-tool audit example/

Validate

Compare your current .env file against the schema. Checks for undefined variables that are required, or variables with no value that are required. You might run this during your deployment process to prevent deploying code that requires some new environment variable which has not been configured.

env-tool validate .env

Sync

Creates or updates an env file.

As the project changes, you may want to update your env file to declare the latest variables. This will overwrite the current env file, but keeps your existing values. New variables are declared with any applicable default values.

env-tool sync .env