fix(@angular/build): emit a warning when outputHashing is set to all or bundles when HMR is enabled

alan-agius4 · alan-agius4 · commit af3b14c4f333 · 2025-07-11T14:15:40.000+02:00
These values are incompatible with HMR. Closes #30697
diff --git a/packages/angular/build/src/builders/dev-server/vite-server.ts b/packages/angular/build/src/builders/dev-server/vite-server.ts
@@ -28,6 +28,7 @@ import { loadProxyConfiguration, normalizeSourceMaps } from '../../utils';
 import { useComponentStyleHmr, useComponentTemplateHmr } from '../../utils/environment-options';
 import { loadEsmModule } from '../../utils/load-esm';
 import { Result, ResultFile, ResultKind } from '../application/results';
+import { OutputHashing } from '../application/schema';
 import {
   type ApplicationBuilderInternalOptions,
   BuildOutputFileType,
@@ -158,6 +159,19 @@ export async function* serveWithVite(
     process.setSourceMapsEnabled(true);
   }
 
+  if (
+    serverOptions.hmr &&
+    (browserOptions.outputHashing === OutputHashing.All ||
+      browserOptions.outputHashing === OutputHashing.Bundles)
+  ) {
+    serverOptions.hmr = false;
+
+    context.logger.warn(
+      `Hot Module Replacement (HMR) is disabled because the 'outputHashing' option is set to '${browserOptions.outputHashing}'. ` +
+        'HMR is incompatible with this setting.',
+    );
+  }
+
   const componentsHmrCanBeUsed =
     browserOptions.aot && serverOptions.liveReload && serverOptions.hmr;
 
