commandbox-modules/commandbox-dotenv

Check for a new `.env` file after certain CommandBox commands

elpete opened this issue · 2 comments

Here's how I envision this one going:

Using both a preCommand and postCommand interceptor, check if the command executed changed the current directory. If it did, check for an .env file. If one is found, load it and inform the user in the console.

This should be fixed by #9 which more generically just loads env vars before any command, but only into the environment context of that command, so they automatically clean up after.

Resolved in v1.6.0 / #9