Skip to content

ng Build wipes output folder clean #6193

Closed
@SanderElias

Description

@SanderElias

Bug Report or Feature Request (mark with an x)

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

Versions.

@angular/cli: 1.0.1
node: 6.10.3
os: linux x64
@angular/animations: 4.1.0
@angular/common: 4.1.0
@angular/compiler: 4.1.0
@angular/core: 4.1.0
@angular/flex-layout: 2.0.0-beta.8
@angular/forms: 4.1.0
@angular/http: 4.1.0
@angular/platform-browser: 4.1.0
@angular/platform-browser-dynamic: 4.1.0
@angular/router: 4.1.0
@angular/upgrade: 4.1.0
@angular/cli: 1.0.1
@angular/compiler-cli: 4.1.0

Repro steps.

put some random files in the dist folder.
ng build
Your files are gone.

The log given by the failure.

none

Desired functionality.

That it leaves the files that are not generated by the CLI alone.
Reason, My project might need for example a webworker, and some other code that's living outside the CLI (like in a ngUpgraded project, not everything is under the CLI's control yet)
Now I need to make sure the build tools run in the right order, otherwise, the CLI will kill my other files.

Additional remark

I think this should be under control of a setting. The current behaviour is fine in a project that's only using the CLI. So the default behaviour should not get changed. I think an option in the .angular-cli.json for this is a good option. An extra cmd-line flag is also fine, however, there are already a lot of those!

Metadata

Metadata

Assignees

Labels

P3An issue that is relevant to core functions, but does not impede progress. Important, but not urgenteffort1: easy (hours)featureIssue that requests a new featureseverity2: inconvenient

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions