env-sync
automates the process of syncing and saving examples of all your
env
files. No more manually updating env samples
$ npm install @ize-302/env-sync -g
$ env-sync
$ npm install @ize-302/env-sync -D
- Insert as script command
// package.json
{
"scripts": {
"env": "@ize-302/env-sync"
}
}
- Run it
$ npm run env
1. Only environmental variables (EV) with values will be synced. EVs without stated values will not be synced.
2. If a new .env file is added while running env-sync, you will have to close the process and run the command again to be able to sync the newly added .env file
3. All generated env examples are stored in the env-examples folder at the root of your working directory
4. For feature requests/bug report, feel free to open a new issue. Will be happy to look into it