prevent ng build from overwriting source files
- Vorherrschende Sprache
- TypeScript
- Sterne
- 27k
- Forks
- 11.8k
- Ø Merge
- 14 Std. 23 Min.
- Gemergte PRs (30 T.)
- 162
Beschreibung
Okay, that one was scarry as hell. I am sooo lucky I pushed my project to GH before building ng sources prepared for prod....
What I did was opening .angular-cli.json and setting
"outDir": "../../",
as I wanted to store built files next to my project so that I could simply exclude project in gradle. Turns out that was a terrible mistake as ng build --prod decided to nuked my whole UI project for good. Yes sir it did. 10 days of work have been completely vanished from my harddrive. Good thing is that I did push it all to git before...
I would strongly suggest to add safety switches preventing self-destruction in the whole ng-cli project.
Beitragsleitfaden
Rechercherichtung
Beginne mit .angular-cli.json und reproduziere das gemeldete Verhalten von ng build --prod unter Verwendung eines outDir von ../../. Verfolge, wie Angular CLI diesen Ausgabepfad verarbeitet, und definiere einen Sicherheitsmechanismus, der destruktive Schreibvorgänge außerhalb des Projekts verhindert.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- angular, typescript
- Bereich
- build-system, cli
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100