Issues with environment variables and Angular2+

[tsonevn]

From @rafaelcmrj on August 21, 2018 20:32

Did you verify this is a real problem by searching the NativeScript Forum and the other open issues in this repo?

Yes

Tell us about the problem

I'm using Angular2+ and the environments file isn't loading the production file when using --release. I've tried --env.prod, --env prod, --env=prod and many other options. None of them worked.

Which platform(s) does your issue occur on?

Both

Please provide the following version numbers that your issue occurs with:

• CLI: 4.1.2
• Cross-platform modules: 4.1.1
• Runtime(s): ios 4.1.0 / android 4.1.3

Please tell us how to recreate the issue in as much detail as possible.

Any app using Angular2+ and environment files.

Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.

The environment files are located under /app/environments/enviroment.ts and /app/environments/enviroment.prod.ts

Copied from original issue: NativeScript/NativeScript#6206

[tsonevn]

Hi @rafaelcmrj,
This issue seems to be related to a missing feature. I will mark this as a feature request and would suggest keeping track on it for further info. In the meantime, you can check this thread.

[derek-fong]

@rafaelcmrj I believe you can achieve this by tweaking your project's webpack.config.js and environment.*.ts, if you are using @nativescript/schematics in your project.

I have written an article to outline the steps required to utilize environment.*.ts in NativeScript Angular's projects in mobile and/or web platforms: https://medium.com/@derekfong/nativescript-angular-setup-environment-ts-for-different-environments-631b4c5219b6