-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support sourcing environment variables from .env
files
#36
Comments
I think this is an easy change to make, but I wonder if it warrants adding a dependency. Current environment flags act like one-off settings and I can't see a team using a On the other hand, in case of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some project support loading environment variables from
.env
files to allow permanent variables to be committed and shared among project members. Examples includecreate-react-app
and Docker Compose. I think it would be great ifyarnhook
did as well. That way, a project team could share a variable such asYARNHOOK_DRYRUN=true
without requiring each member to set it in a global.bashrc
file.Though this may seem to limit individual preference in environment variables,
yarnhook
could also recognize.env.local
, which overrides.env
and is usually listed in.gitignore
The text was updated successfully, but these errors were encountered: