Question: Possible to load multiple .env files into the shell?

Question: Is it possible to load multiple .env files into the shell?

npx dotenv-extended --path=first.env dotenv-extended --path=second.env node herro.js

Or something like:

npx dotenv-extended --path=first.env,second.env node herro.js

[goatandsheep]

@mvastola so like this? https://github.com/keithmorris/node-dotenv-extended/pull/50

[mvastola]

I was about to post this same feature request. The idea would be to allow for multiple layers of defaults/settings, as provided by dotenv-flow (which is fairly popular) as well as similar modules.

These other modules, however, aren’t easily made compatible with dotenv-extended, however, without allowing the overriding of values already in the environment. (Or otherwise by saving the original environment and re-applying it after the changes in this module.)

Implementing this feature a really simple change as well. The vast majority of the change is simply updating src/index.js to say

let envFiles = [];
[ options.defaults, options.path ].forEach(files => {
  if (!files || files.length === 0) return;
  if (!Array.isArray(files)) files = [ files ];
  envFiles.push(...files);
});
let configData = files.reduce((accumulator, file) => {
  let fileData = loadEnvironmentFile(file, options.encoding, options.silent);
  return { ...accumulator, ...fileData };
});

Beyond that, pretty much only CLI argument parsing would need to be tweaked, and documentation would need to be updated.