load-env changelog

Changelog History

Page 1

• v0.2.1.0 Changes

  • Don't override values already set in the environment

  Given a hypothetical program load-env, which uses one of our loadEnv functions on stdin:

  Previously,

    FOO=bar load-env <<EOM
    FOO=bat
    EOM
  

  would override FOO to bat when load-env ran. But now, it will see FOO is already bar and leave it.

  This is better behavior under the assumption that a .env file is meant to specify defaults in the case of nothing explicit. When there are explicit values in the environment, it's most likely that our user indeed wants them respected.

• v0.2.0.2 Changes

  • 👍 Allow lower-case characters in variable names @denibertovic

• v0.2.0.1 Changes

  • 📚 Packaging and documentation updates

• v0.2.0.0 Changes

  • Traverse up parent directories to find the .env file

• v0.1.2 Changes

  • ⚡️ Packaging updates

• v0.1.1 Changes

  • 📜 Parse variables names more strictly

• v0.1.0 Changes

  • Don't fail on an empty file
  • Ignore any invalid lines, not specifically things that look like comments

• v0.0.4 Changes

  • 👻 Don't throw an exception if the .env file is missing

• v0.0.3 Changes

  • Variable names can contain underscores

• v0.0.2 Changes

  • ⬇️ Drop support for GHC < 7.8

• 1
• 2
• Next ›
• Last »