I built this package while working on an app that I deployed to production, staging and my local dev environment. I had a couple of scripts (one to deploy, one to migrate the database, etc.) that I wanted to run, but I didn't want to have to maintain one script for each environment doing almost the same but to different endpoints.
So, I built a simple CLI that reads one or more .env files and spawns a new child process running an NPM script from the package, with the environment variables extended with the contents of the files.
It also supports expansion, where one file use the value defined in another file.
Please see the README for more details and usage and consider giving it a spin in your next project if you're faced with a similar problem.
So, I built a simple CLI that reads one or more .env files and spawns a new child process running an NPM script from the package, with the environment variables extended with the contents of the files.
It also supports expansion, where one file use the value defined in another file.
Please see the README for more details and usage and consider giving it a spin in your next project if you're faced with a similar problem.