Open marklagendijk opened 9 hours ago
I realize that this bug report is very specific and hard to reproduce. I reported it anyway because:
This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?
You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app
and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.
Command
build
Is this a regression?
The previous version in which this bug was not present was
18.2.12
Description
After upgrading to Angular 19 our Azure Pipelines CI/CD build started failing. The Angular build fails because it cannot find/parse
tsconfig.app.json
.The failure happens under very specific circumstances. I will describe the high level conditions here, and go into more detail in the 'Minimal Reproduction' below.
.esproj
project is used for the Angular application.The baffling thing for me is that the exception mentions a '.NET build system specific'-folder:
PROJECT_NAME/obj/Debug
while I verified that the current working directory in which thenpm run build
command is executed is actually thePROJECT_NAME
folder. So where is the Angular build system getting this folder from? And why is it using that folder instead of the current working directory?Minimal Reproduction
ng new repro-app
.application.esproj
with the following contents:ubuntu-24.04
vmImageException or Error
Your Environment
Anything else relevant?
No response