Index.html is produced locally when outputPath is a remote folder
@clydin já está trabalhando nisso.
Desde 14/1/2021.
Avaliação
Esta issue ainda não foi avaliada.
Descrição
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.
- Linguagem predominante
- TypeScript
- Estrelas
- 27k
- Forks
- 11.8k
- Merge médio
- 17h 25min
- PRs com merge (30d)
- 183
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de angular/angular-cli
-
area: @angular/build gemini-triaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 74/100
angular/angular-cli#33955 ·
-
area: @angular/cli gemini-triaged
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
angular/angular-cli#33055 · 1 comentário · 3 reações ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34131 · 1 responsável ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34130 · 1 responsável ·
-
angular/build:library area: @angular/build gemini-triaged
angular/angular-cli#34128 · 1 responsável ·
Todas as issues de angular/angular-cli
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
-
bug v2
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
modelcontextprotocol/inspector#2458 · 1 comentário ·
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 70/100
carbon-design-system/ibm-products#9907 ·