Custom environments flags not working

[AnthonyGiretti]

I'm using Angular-cli 1.4.4, and i'm unable to use environments properly

I have this :
"environments": {
"dev": "environments/environment.ts",
"prod": "environments/environment.prod.ts",
"qa": "environments/environment.qa.ts"
}

When I build with my qa environment it uses prod configuration
I ran this: ng build --env=qa

[filipesilva]

@AnthonyGiretti can you put up a repository on github that shows this problem happening please? I cannot reproduce locally with the information you have given.

[AnthonyGiretti]

Hi @filipesilva thank you for your reply!

Yes you can find it here
https://github.com/AnthonyGiretti/Angular4-IgniteUI.git

Can't wait to hear from you!

Anthony

[bytemonkio]

I am having a similar issue

ng build --env=prod is always picking environment.ts instead of environment.prod.ts is this a bug?

I guess its because main.ts imports environment.ts by default
import { environment } from './environments/environment';
If main.ts imports environment.prod.ts, that gets picked up all the time.
import { environment } from './environments/environment.prod.ts';
https://stackoverflow.com/questions/46573559/angular4-enable-production-mode

[AnthonyGiretti]

Hi, any update on this?

[slucas-nwx]

I'm having the same issue. This was working before I updated to the latest version of angular 4. My project was started in Angular 4.2

I believe as @hmajumdar that the main is not getting overridden.

Example of my setup:
"environmentSource": "environments/environment",
"environments": {
"local-us": "environments/us/environment.local.ts",
"dev-us": "environments/us/environment.dev.ts",
"qa-us": "environments/us/environment.qa.ts",
"prod-us": "environments/us/environment.prod.ts",
"local-au": "environments/us/environment.local.ts",
"dev-au": "environments/au/environment.ts",
"qa-au": "environments/au/environment.qa.ts",
"prod-au": "environments/au/environment.prod.ts"
}

[pearpages]

You need to set the envName in the environment Object for all the environments , something like this

export const environment = {     
    production: true, 
    apiURL : '/offer-screener-web/'   
    envName: 'prod' 
};

[slucas-nwx]

@pearpages Yea I know that. Each file has it's own environment values all with the same object attributes. The CLI just isn't loading the file that is specified in the angular-cli.json

ie. ng build --env=dev-us like I have in my setup. It used to until I updated to the latest version.

[guilhermejcgois]

we are using 1.4.9 here and seems that all is ok, and we also use a path mapping on tsconfig too...

      "environmentSource": "environments/environment.ts",
      "environments": {
        "local": "environments/environment.local.ts",
        "dev": "environments/environment.ts",
        "qa": "environments/environment.qa.ts",
        "prod": "environments/environment.prod.ts"
      }

[slucas-nwx]

Here's an example of my dev configs.

//"dev-us": "environments/us/environment.dev.ts"
export const environment = {
production: false,
envName: 'dev',
apiUrl: 'https://max.biz/',
translationAssetPath: '/bundles/maxangular/assets/i18n/',
defaultLocale: 'en_US',
supportedLocalesPath: '/bundles/maxangular/assets/locales/locales.us.json'

};

Is there something obviously wrong?