question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

--delete-output-path no longer working with ng serve

See original GitHub issue

Versions

<!--
Output from: `ng --version`.
If nothing, output from: `node --version` and `npm --version`.
  Windows (7/8/10). Linux (incl. distribution). macOS (El Capitan? Sierra?)
-->

Angular CLI: 6.0.0-rc.5
Node: 8.11.1
OS: win32 x64
Angular: 6.0.0-rc.5
... cli, common, compiler, compiler-cli, core, forms, http
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.5.7
@angular-devkit/build-angular     0.5.7
@angular-devkit/build-optimizer   0.5.7
@angular-devkit/core              0.5.7
@angular-devkit/schematics        0.5.7
@ngtools/json-schema              1.1.0
@ngtools/webpack                  6.0.0-rc.5
@schematics/angular               0.5.7
@schematics/update                0.5.7
rxjs                              6.0.0-uncanny-rc.7
typescript                        2.7.2
webpack                           4.5.0

Repro steps

  • Create a new Angular App
  • Try to run it using ng serve --host=0.0.0.0 --port=8100 --delete-output-path=false

Observed behavior

<!-- Normally this includes a stack trace and some more information. -->

Error is returned saying ```Unknown option: '--deleteOutputPath'```. There is no stack trace available

Desired behavior

Based on the source, I would expect that flag or its alias ‘dop’ to still work.

Mention any other details that might be useful (optional)

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:6

github_iconTop GitHub Comments

5reactions
timfogarty-row8commented, May 30, 2018

What if the output path is under git control? Now the entire folder gets wiped out, including the .git folder.

3reactions
Selupsiscommented, Jun 27, 2018

Our build also requires work to be done in the output folder before the actual build, so the removal of this option is a big impact… Any feasible workarounds?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Where to specify delete-output-path? - angular - Stack Overflow
I understand there is a delete-output-path parameter that can be put on the command line to ng build . Is it possible to...
Read more >
Implementing Angular's missing “delete output path after build ...
The problem​​ I'm talking about the fact that when you build your Angular app, it first deletes your output path, then builds your...
Read more >
Angular workspace configuration
Path values given in the configuration are relative to the root workspace ... the Angular CLI never writes files outside of the project...
Read more >
Angular CLI - ng build Command - Tutorialspoint
Sr.No. Option & Syntax Description 2 ‑‑baseHref=baseHref Base url for the application being built. 9 ‑‑deployUrl=deployUrl URL where files will be deployed. 17 ‑‑localize=true|false
Read more >
ng build - Angular
Option Description Value Type Default Value ‑‑aot Build using Ahead of Time compilation. boolean false ‑‑base‑href Base url for the application being built. string ‑‑delete‑output‑path Delete...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found