-
Notifications
You must be signed in to change notification settings - Fork 16
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
Variable expansion in .env
does not work any more
#47
Comments
On a fresh nx install I cannot reproduce the problem either but on my project if I'm switching between 16.0.2 and 16.1, it works / it does work, that is weird... I have noticed that |
@chihab I think I spotted the issue: the expansion does not work in the |
That's right, that happens because you run the application using nx command (with a target); when doing that nx does read the .env file and populates process.env before running the @ngx-env/builder, when he builder is run it won't override the env var since already present in process.env. If you run the builder directly (wihtout using the nx command), you won't have the issue. The only workaround is to name .env files differently so that nx does not seem them, for example .env.app or the like, you can specify the list of files using the "files". There is a nx working example in the examples folder. |
It seems that since the 16.1, variable expansion does not work anymore.
NG_APP_URL used to be
https://develop.example.com
until 16.0.2 and now it ishttps://${MY_ENV}.example.com
By the way, thanks for this great project!
👍
The text was updated successfully, but these errors were encountered: