fix(platform-browser): resolve component resources before bootstrapping in JIT mode (#62758)

crisbeto · NothingEverHappens · commit 2fd1f7beb5e5 · 2025-07-23T11:05:20.000-04:00
Currently if the app has some external resources and it gets bootstrapped in JIT mode, the user will get an error about calling `resolveComponentResources`. These changes add a call to `resolveComponentResources` automatically inside `bootstrapApplication`. Note that we don't need similar logic for `bootstrapModule`, because it calls into `compileNgModuleFactory` internally which in turn calls `resolveComponentResources`. PR Close #62758
diff --git a/packages/platform-browser/src/browser.ts b/packages/platform-browser/src/browser.ts
@@ -38,6 +38,7 @@ import {
   ɵTESTABILITY as TESTABILITY,
   ɵTESTABILITY_GETTER as TESTABILITY_GETTER,
   inject,
+  ɵresolveComponentResources as resolveComponentResources,
 } from '@angular/core';
 
 import {BrowserDomAdapter} from './browser/browser_adapter';
@@ -125,7 +126,20 @@ export function bootstrapApplication(
   rootComponent: Type<unknown>,
   options?: ApplicationConfig,
 ): Promise<ApplicationRef> {
-  return internalCreateApplication({rootComponent, ...createProvidersConfig(options)});
+  const config = {rootComponent, ...createProvidersConfig(options)};
+
+  // Attempt to resolve component resources before bootstrapping in JIT mode,
+  // however don't interrupt the bootstrapping process.
+  if ((typeof ngJitMode === 'undefined' || ngJitMode) && typeof fetch === 'function') {
+    return resolveComponentResources(fetch)
+      .catch((error) => {
+        console.error(error);
+        return Promise.resolve();
+      })
+      .then(() => internalCreateApplication(config));
+  }
+
+  return internalCreateApplication(config);
 }
 
 /**
