With standard CLI build, we can rely on different environment.ts files. For example: environment.staging.ts. angular.json allowed replacement of default environment.ts file with the environment specific one depending on configuration when running ng build --configuration=staging for example.
How this can be achieve when migrating to Bazel? Adding bazel to project basically deletes everything related to specific configurations and file replacements.
Thanks for this great introduction!
Some questions for you!
With standard CLI build, we can rely on different
environment.tsfiles. For example:environment.staging.ts.angular.jsonallowed replacement of defaultenvironment.tsfile with the environment specific one depending on configuration when runningng build --configuration=stagingfor example.How this can be achieve when migrating to Bazel? Adding bazel to project basically deletes everything related to specific configurations and file replacements.
I have the same problem, any solution for this issue?