Index.html is produced locally when outputPath is a remote folder
@clydin ci sta già lavorando.
Dal 14/1/2021.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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.
- Lingua principale
- TypeScript
- Stelle
- 27k
- Fork
- 11.8k
- Merge medio
- 17h 25m
- PR unite (30g)
- 183
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di angular/angular-cli
-
area: @angular/build gemini-triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
angular/angular-cli#33955 ·
-
area: @angular/cli gemini-triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
angular/angular-cli#33055 · 1 commento · 3 reazioni ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34131 · 1 assegnatario ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34130 · 1 assegnatario ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34128 · 1 assegnatario ·
Tutte le issue di angular/angular-cli
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
fil-donadoni/tolaria#4409 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
corsairdev/corsair#1764 ·