Skip to content

ng serve looses --env argument after code change trigger a rebuild #6201

@RodrigoMattosoSilveira

Description

@RodrigoMattosoSilveira

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.0.0-rc.4
node: 6.9.4
os: darwin x64
@angular/animations: 4.1.1
@angular/common: 4.1.1
@angular/compiler: 4.1.1
@angular/compiler-cli: 4.1.1
@angular/core: 4.1.1
@angular/forms: 4.1.1
@angular/http: 4.1.1
@angular/platform-browser: 4.1.1
@angular/platform-browser-dynamic: 4.1.1
@angular/platform-server: 4.1.1
@angular/router: 4.1.1
@angular/cli: 1.0.0-rc.4

Repro steps.

  • create a new environmental file, environment.ua.ts', and configure it in .angular-cli.json` accordingly.
  • run ng serve --env=ua
  • observe that the ua is loaded, as expected
  • change the software
  • observe that the default environment is loaded

The log given by the failure.

  • the observed behavior is that the build reverts back to the default environment!
  • there are no logs

Desired functionality.

The automatic build preserves the ua environment!

Mention any other details that might be useful.

I added a note to a similar issue, 6132 to the same effect.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions