We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I ran into the issue when using this in a script.
On first run of the script, the .env is read and $env is populated. Upon re-run, it fails to load because it thinks we already have (same dir)
.env
$env
Set-PsEnv/Set-PsEnv.psm1
Lines 35 to 40 in 1be3a96
The text was updated successfully, but these errors were encountered:
My workaround was to just clear $Global:PreviousDir = "" before calling Set-PsEnv
$Global:PreviousDir = ""
Set-PsEnv
Sorry, something went wrong.
I ran into the same issue and found the same workaround.
It would be ideal to have a -Force flag so that the module loads .env file regardless of whether it is the same folder or not.
-Force
CC: @rajivharris Thank you for creating this package. Much appreciated!
No branches or pull requests
I ran into the issue when using this in a script.
On first run of the script, the
.env
is read and$env
is populated. Upon re-run, it fails to load because it thinks we already have (same dir)Set-PsEnv/Set-PsEnv.psm1
Lines 35 to 40 in 1be3a96
The text was updated successfully, but these errors were encountered: