Azure / Azure/static-web-apps-cli

swa init does not detect Angular application-builder output directory

Offen
#843 1 Kommentar 1 Reaktion 1 zugewiesene Person Beansprucht von @Timothyw0 Auf GitHub ansehen
command: init priority: high (P0) runtime: static scope: app type: bug version: ga
Vorherrschende Sprache
TypeScript
Sterne
668
Forks
156
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

**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.

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.