Add support for .env.development file #894
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ehmicky
approved these changes
May 11, 2020
| const envFile = path.resolve(projectDir, '.env') | ||
|
|
||
| try { | ||
| if ((await fileStat(envDevelopmentFile)).isFile()) return envDevelopmentFile |
There was a problem hiding this comment.
That could be used too: https://github.com/sindresorhus/locate-path#usage
return locatePath([envDevelopmentFile, envFile])
|
:D thank you for this! |
|
@wesbos Glad you found it useful 😊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
- Summary
Fixes: #876
- Test plan
- Description for the changelog
getEnvFileto return.env.developmentor fallback to.envfilegetEnvFile- A picture of a cute animal (not mandatory but encouraged)
🦆