Azure / Azure/static-web-apps-cli

swa init does not detect Angular application-builder output directory

Aperta
#843 1 commento 1 reazione 1 assegnatario Rivendicata da @Timothyw0 Vedi su GitHub
command: init priority: high (P0) runtime: static scope: app type: bug version: ga
Lingua principale
TypeScript
Stelle
668
Fork
156
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

**Describe the bug**

I have an Angular v18 app created with:

```bash
npx ng new app-name
```

Running `swa init --yes` sets the outputLocation to "dist\\app-name".
The "angular.json" show projects > app-name > architect > build > options > outputPath is dist/app-name (so it's technically correct)

A recent change in the Angular system now places the files in dist/app-name/browser. This location is configurable. This is explicitly the case when the default builder (@angular-devkit/build-angular:application) is used. See https://github.com/angular/angular-cli/issues/26304 for a discussion of the problem.

**To Reproduce**
Steps to reproduce the behavior:

```bash
ng new app-name
cd app-name
swa init --yes
```

**Expected behavior**

The SWA CLI should properly detect the output path based on the angular.json settings.

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.