Index.html is produced locally when outputPath is a remote folder
@clydin arbeitet bereits daran.
Seit 14.1.2021.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
UPDATE 2020-12-20: I discovered this morning that the index.html files ARE being produced, but they are being pushed to my local machine instead of the remove machine.
From my angular.json: "outputPath": "\\\\remote-computer-name\\all-projects-folder\\project-folder"
Files SHOULD be copying to C:\all-projects-folder\project-folder. on the REMOTE machine. Instead, files are copying to C:\remote-computer-name\all-projects-folder\project-folder on my LOCAL machine
🐞 Bug report
Command (mark with an x)
- new
- build
- serve
- test
- e2e
- generate
- add
- update
- lint
- extract-i18n
- run
- config
- help
- version
- doc
Is this a regression?
No. Discovered in 9.1.7. Updated to latest hoping to fix the problem. Still exists.Description
Title says it all. When run ng build, everything works as expected. When I run ng build --configuration=remote-build, the build completes without errors and all files are pushed to the remote folder EXCEPT index.html.
🔬 Minimal Reproduction
Link to repro project here: https://github.com/joshorvis/remote-build. (Only change from the default ng new is a new target added in angular.json)
- set up a folder you can access on another machine. confirm file permissions aren't blocking writes from your local machine.
- npm install project on local machine. Update angular.json line 86 with the network path to your remote folder.
- run ng build. See index.html in local project folder /dist/remote-build
- run ng build --configuration=remote-build. See everything but index.html
- cry with me.
UPDATE: It appears that mapping the remote folder to a network drive letter will produce the index.html as expected.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 27k
- Forks
- 11.8k
- Ø Merge
- 17 Std. 25 Min.
- Gemergte PRs (30 T.)
- 183
Beitragsleitfaden
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus angular/angular-cli
-
area: @angular/build gemini-triaged
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
angular/angular-cli#33955 ·
-
area: @angular/cli gemini-triaged
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
angular/angular-cli#33055 · 1 Kommentar · 3 Reaktionen ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34131 · 1 zugewiesene Person ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34130 · 1 zugewiesene Person ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34128 · 1 zugewiesene Person ·
Alle Issues in angular/angular-cli
Ähnliche Issues
-
blocklist removal
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
pastelsky/bundlephobia#1122 ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 75/100