Tsconfig.json in final war file

Hello all! Why vaadin include tsconfig.json in root context of war file? For example, in production mode https://localhost:8080/tsconfig.json

Vaadin does not produce a WAR file by itself. And development files are not added to the production bundle.

Can you provide more details about your configuration? Or provide a reproducible example?

Vaadin version 24.9.11 production mode build. Although the tsconfig.json file itself is not in the war file

I cannot reproduce with the Vaadin starter project.
If I try to access tsconfig.json I get a Could not navigate to 'tsconfig.json' page.

You are right if you start the project with https://github.com/vaadin/skeleton-starter-flow/tree/v24 this artifact does not exist

I also tried to enable frontendHotdeploy, so the tsconfig.json file is generated, but I still get the “Could not navigate” message,

Edit: even with forceProductionBuild=true the json file is not served at runtime

Only in 2 files mention tsconfig.json in war file:
circular-progress-bar-flow-1.3.2.jar
flow-server-24.9.12.jar

Very strange

The problem is exactly in the CircularProgressBar Flow add-on. It contains the tsconfig.json file in the META-INF/resources folder, which is directly served by the servlet container.