Added options.node_env that refers process.env.NODE_ENV by default

[MasonRhodesDev]

I went ahead and put together the changes we talked about in issue 5.

If this is up to standards and keeps within the goals of this module please consider reviewing.

Thanks!

[kerimdzhanov]

Also, don't forget to squash your commits into a single one, and please follow the angular commit message conventions, because we use conventional-changelog to generate the CHANGELOG.md when releasing a new versions. Also you can refer the issue #5 in your commit message.

Summarizing the above, I want this PR to be a single commit with message like:

feat(options): add `options.node_env` implementation, closes #5

[MasonRhodesDev]

I've made all the changes we talked about above. But in the process we did end up removing the line that sets process.env.NODE_ENV to options.default_node_env so this
```describe('when the default_node_env option is provided', () => {````
test fails now.

Should I replace the setter that we removed or leave setting NODE_ENV up to the user?

[kerimdzhanov]

Test shouldn't be changed on removing process.env.NODE_ENV, sorry, I tough it's obvious :)
We just shouldn't refer process.env.NODE_ENV nowhere except our one-liner, the idea is to be totally independent from process.env.NODE_ENV when we provide our custom node_env as an option. In other words, we shouldn't touch the variable at all, like it doesn't exists.

[MasonRhodesDev]

Un-related to the code, but what would be the best option for addressing the original issue you presented? to follow angular commit standards would the best option after the other issues are fixed to re-submit a new pull request or is there a way to address that here? (to be honest I don't have much experience contributing to other's projects on github and I really appreciate your patience with me thus far)

[kerimdzhanov]

You can try to git squash then push --force to the same branch, I'm not sure does it work with github, but with bitbucket it works.

[MasonRhodesDev]

ok, I'll try that after I finish

[kerimdzhanov]

Or maybe it would be better to try squash merge PR with github. Leave it as is for now.

[kerimdzhanov]

Yes, exactly, we can do squash merge 👍

[MasonRhodesDev]

ok, I think its ready for review number 2.

(its also getting late for me, so if there are anymore changes that need to be made I'll probably address them tomorrow)

[kerimdzhanov]

Everything else looks perfect 👍

[kerimdzhanov]

@solaris765, good job 👍
You are the first contributor of the project, thank you! 🍻
Don't forget to ⭐️ the project you've contributed to ;)

[MasonRhodesDev]

Awesome! Done!

[kerimdzhanov]

@solaris765, I've released a new candidate v0.2.0-rc.1. You can try it.

$ npm install "dotenv-flow@latest"

or

$ yarn add dotenv-flow

Let me know if you find any related bugs.

[MasonRhodesDev]

Got it. I'll try it now. I have a use case that's currently referencing an earlier version of my git fork that I can move over for testing