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
Do not automatically unload direnv for subfolders (that are not allowed) #877
Comments
I'm using a very similar technique in our monorepo:
and since 2.30.x I'm not able to keep envs loaded inside the |
Solution: #878 |
Yep, same here. The auto-unload is causing issues, and it can't even be worked around by denying the problematic Seems like this was pre-existing behavior, but |
This only fixes the issue if using an .env in the subdirectory when having a blocked .envrc in the child directory the parent directory's .envrc still get's unloaded. |
The autoload .env (#845) broke our monorepo that uses nix.
Many sub projects that have
.env
.a
andb
no longer have access to tools provided by<repo>/.envrc
how is one suppose to handle this now?Expected behavior
To keep the context of the already initialized direnv. That is do not unload the env on subfolder that just happen to contain a
.env
file if it is not explicitly allowed.Environment
Let me know of more info is needed.
Cheers
The text was updated successfully, but these errors were encountered: