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

dotenv-safe-select

v2.0.0

Published

> Allows to select dotenv files and run project with checks against predefined set of env variables during development.

Downloads

37

Readme

Select dotenv file safe

Allows to select dotenv files and run project with checks against predefined set of env variables during development.

During development select any of .env files located into project root and do check current env variables against .env.example file with dotenv-safe.

Installation

yarn add dotenv-safe
yarn add --dev dotenv-safe-select

Usage

  • There only one file .env.example which needs to be checked in with version control and used as a single source of truth to check for present env variables.

  • Create other dotenv files like .env.local, .env.staging, .env.production etc. which are not checked in version control.

  • Issue development command for example yarn dotenv-safe-select -- next dev.

  • Optionally it is possible to pass direct path to dotenv file like so yarn dotenv-safe-select --path .env.mine -- next dev.

  • Select dotenv file you would like run your development against.

  • Profit :palm_tree:

Inspired by donenv-flow.

Note: the command passed to dotenv-safe-select executed as a child process spawn. I'm thinking to add child process fork support to be able execute .js files.