Verify against example

[halvardssm]

Hi @crowlKats ! I've been using your lib a bit more, and I did another addition. Let me know if you are ok with this feature as well!

[halvardssm]

Another addition (haven't made it yet though), could be to have an option of using the example file as default options. What do you think about this?

[halvardssm]

Hi @crowlKats ! I made a small update to the PR, please let me know if this is still within your vision of the module or if you want any changes 😄

[crowlKats]

@halvardssm first off, i am extremely sorry for not having reviewed this earlier; was going to do it the afternoon you opened it, but ended up being busy for a while and then completely forgot about it.
Secondly, what exactly is the usecase for this?

[halvardssm]

@crowlKats No worries! I also forgot about this PR until I was using denv the other day. So the usecase for this includes when you have advanced config, multiple pipelines and environments, and you are including a .env.example file in your repository.

verifyAgainstExample: The example file can be used to validate the environment at the launch stage rather than during runtime. Say you need a secret for one specific call and it is only used occasionally, meaning you won't catch the missing env before you need it.

defaultToExample: The example file can include default values to use with development.

exampleFile: In case your .env.example is not in the root of the project directory.

Of course, all of these usecases might not be that widely used, but I needed them, so there might be others which might need them too.

[crowlKats]

Oh I see. Well, I don't mind having them, so lets add them!