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

@joe_six/multi-env-cmd

v0.0.3

Published

running scripts in ad-hoc blended enviroments

Downloads

6

Readme

Ad-hoc mixing of multiple .env files into an Environment to run shell Commands in

No a big thing, just mixing up multiple .env config files into an ad-hoc enviroment to run your application in. Usually in development, not production.

This for example makes up an env on the fly combined from three files:

$ multi-env .env.sqs.dev .env.db.local .env.saas.staging -- ./bin/app-under-development

Like when you have a programm which connects with two different databases, an AWS SQS queue and a external SaaS API. To run this script in dev mode you need to configure all of them, but depending on what you actually work on, you need a different set-up. In this case this are three envs combined, and possibilities multiply. Add test, staging and production and combinations go up beyond what you can handle in a single .env file.

Add as many .env files you like, end that list with -- and have your regular cmdline following right after it. The above example results in constructing and executing this shell command:

$ (set -a; source .env.sqs.dev && source .env.db.local && source .env.saas.staging && ./bin/app-under-development)

Frameworks like laravel support a .env file directly, and in testing even overload it automatically from .env.testing. This script is for such needs, but in a generic way. Packages like .dotenv do similar things, but for from inside a node.js app itself. This here is for the cmdline.

All of this is guided by the idea of 12 Factors, go read it, if you haven't. Seriously.

have fun