process.envSee original GitHub issue
process.env is not great as the used env variables seem to be not declared anywhere. We should use
cross-env for testing purposes and use some config for setting them instead of using
- Created 5 years ago
- Comments:7 (1 by maintainers)
Top GitHub Comments
I don’t think we should have a
.env committed into the repo.
Is there a reason why those links are set using environment variables (slack etc.)? I don’t think those should be set by the environment.
If anything, you could set default values if the environment variables aren’t detected. We can have a sample
.env file that developers can use to write their own and include instructions in the repo. But environment variables should be for things like… the
CODING_COACH_API url, or whatever client API keys we’re using (like the Google Analytics example).
Just my two cents! 🤷♂️
Exactly. dot-env are normally meant for credentials and user specific settings.