Hacktoberfest 2026：維護者為十月標記出來的 issue，仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Index.html is produced locally when outputPath is a remote folder

未關閉
#19,653 3 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

@clydin 已經在處理了。

開始於 2021年1月14日。

評估

這個 Issue 還沒有評估資料。

描述

area: @angular-devkit/build-angular
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)

  1. set up a folder you can access on another machine. confirm file permissions aren't blocking writes from your local machine.
  2. npm install project on local machine. Update angular.json line 86 with the network path to your remote folder.
  3. run ng build. See index.html in local project folder /dist/remote-build
  4. run ng build --configuration=remote-build. See everything but index.html
  5. cry with me.

UPDATE: It appears that mapping the remote folder to a network drive letter will produce the index.html as expected.

主要語言
TypeScript
星號
27k
分支
11.8k
平均合併
17 小時 25 分鐘
30 天內合併 PR
183

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

angular/angular-cli 的其他 Issue

查看 angular/angular-cli 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。