Load .env files

[ericclemmons]

It'd be cool if this support .env files or node-config by default.

[blakerutledge]

I needed this functionality a bit ago, but didnt have time to do anything worth a PR, i.e., I changed the default behavior of this module in a non-optional way and added a dependency.. so my fork loads from the .env file that is siblings with, or in a parent folder of the package.json file. Figured id leave this here in case it helps anyone: https://github.com/blakerutledge/per-env

[ericclemmons]

I think this is brilliant! Great job on this, and .env coupling is correct IMO.

…

On Mon, Oct 29, 2018, 11:02 PM Blake Rutledge ***@***.***> wrote: I needed this functionality a bit ago, but didnt have time to do anything worth a PR, i.e., I changed the default behavior of this module in a non-optional way and added a dependency.. so my fork loads from the .env file that is siblings with, or in a parent folder of the package.json file. Figured id leave this here in case it helps anyone: https://github.com/blakerutledge/per-env — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#12 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA7ThHhp8eYI1oiR4Ra6neIFoF7cMPsks5up-uSgaJpZM4T0QA9> .

[blakerutledge]

Ah thanks mate! Just ran into a lil blocker this morning, so added a feature that helps me out -- you can now specify an .env key besides the default NODE_ENV, just by passing a parameter in npm script:

{
    "main": "per-env CUSTOM_KEY",
    "main:custom1": "node custom1.js",
    "main:custom2": "node custom2.js"
}

in .env:

  NODE_ENV=dev
  SUB_APP=subapp1

[chuahcheeshian]

@ericclemmons

NODE_ENV in .env file is supported by by-node-env since v1.2.0.

Please have a look if it helps.