environment variables

I’m submitting a … (check one with “x”)

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please check the repository for a similar issue or PR before submitting -->
[ ] Support request => <!-- Please check the repository for a similar issue or PR before submitting -->
[x] Feature request
[ ] Documentation issue or request

Current behavior I cant find a way to set variables depending on builds

Expected/desired behavior A way to add something like environment variables for the development and production builds.

Minimal reproduction of the problem with instructions NA

What is the motivation / use case for changing the behavior? Set an API URL on localhost or some dev URL, and use another one for production, maybe the same way the angular-cli sets them up in the environments/ folder

Environment

• Angular version: 4.3.0

• Browser:

• Chrome (desktop) version XX
• Chrome (Android) version XX
• Chrome (iOS) version XX
• Firefox version XX
• Safari (desktop) version XX
• Safari (iOS) version XX
• IE version XX
• Edge version XX

• For Tooling issues:

• Node version: 8.4.0
• Platform: Windows

• Others: NA

[juanpmarin]

@kaoz70 https://webpack.js.org/plugins/normal-module-replacement-plugin/ Using that plugin it can be done, having multiple environment files like angular-cli does

[fulls1z3]

#507