Azure / Azure/static-web-apps-cli

swa init does not detect Angular application-builder output directory

Abierto
#843 1 comentario 1 reacción 1 asignado Reclamado por @Timothyw0 Ver en GitHub
command: init priority: high (P0) runtime: static scope: app type: bug version: ga
Lenguaje dominante
TypeScript
Estrellas
668
Forks
156
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

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

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.