Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ng Build wipes output folder clean #6193

Closed
SanderElias opened this issue May 5, 2017 · 1 comment · Fixed by #6186
Closed

ng Build wipes output folder clean #6193

SanderElias opened this issue May 5, 2017 · 1 comment · Fixed by #6186
Assignees
Labels
effort1: easy (hours) feature Issue that requests a new feature P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity2: inconvenient

Comments

@SanderElias
Copy link

SanderElias commented May 5, 2017

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!

filipesilva added a commit to filipesilva/angular-cli that referenced this issue May 5, 2017
@filipesilva filipesilva self-assigned this May 5, 2017
@filipesilva filipesilva added effort1: easy (hours) P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity2: inconvenient feature Issue that requests a new feature labels May 5, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this issue May 5, 2017
filipesilva added a commit to filipesilva/angular-cli that referenced this issue May 8, 2017
dond2clouds pushed a commit to d2clouds/speedray-cli that referenced this issue Apr 23, 2018
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 7, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
effort1: easy (hours) feature Issue that requests a new feature P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent severity2: inconvenient
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants