From b5e9cb4e3e03218d008ef445edf9a81eaf9ec78e Mon Sep 17 00:00:00 2001
From: Alan Agius <17563226+alan-agius4@users.noreply.github.com>
Date: Fri, 25 Apr 2025 06:47:19 +0000
Subject: [PATCH] fix(@angular/build): ensure `com.chrome.devtools.json` is
 consistently served after initial run

Previously, `com.chrome.devtools.json` was generated and served correctly on the first run, but subsequent `ng serve` runs failed to serve the file unless the Angular cache was cleared. This change addresses the inconsistency.
---
 .../src/tools/vite/middlewares/chrome-devtools-middleware.ts   | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/packages/angular/build/src/tools/vite/middlewares/chrome-devtools-middleware.ts b/packages/angular/build/src/tools/vite/middlewares/chrome-devtools-middleware.ts
index 7f063a2e2c9a..43c5bed2edf9 100644
--- a/packages/angular/build/src/tools/vite/middlewares/chrome-devtools-middleware.ts
+++ b/packages/angular/build/src/tools/vite/middlewares/chrome-devtools-middleware.ts
@@ -38,7 +38,8 @@ export function createChromeDevtoolsMiddleware(
     if (!devtoolsConfig) {
       // We store the UUID and re-use it to ensure Chrome does not repeatedly ask for permissions when restarting the dev server.
       try {
-        const devtoolsConfig = readFileSync(devtoolsConfigPath, 'utf-8');
+        devtoolsConfig = readFileSync(devtoolsConfigPath, 'utf-8');
+
         const devtoolsConfigJson: DevToolsJson = JSON.parse(devtoolsConfig);
         assert.equal(projectRoot, devtoolsConfigJson?.workspace.root);
       } catch {