Azure / Azure/static-web-apps-cli

swa init does not detect Angular application-builder output directory

Open
#843 1 comment 1 reaction 1 assignee Claimed by @Timothyw0 View on GitHub
command: init priority: high (P0) runtime: static scope: app type: bug version: ga
Dominant language
TypeScript
Stars
668
Forks
156
PR merge metrics
No merged PRs in 30d

Description

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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.