build: update prerender test to work with ESM APF v13 packages

This commit updates the pre-render test to work with APF v13 package
output which is strict ESM. Since the test runs inside Node, we would
need to update our test to run in ESM as well. This is not possible
with the Bazel NodeJS rules yet, and also there are a couple of more
issues with running ESM devmode directly in NodeJS:

* ESM requires an explicit extension for releative imports. TypeScript
  will not add an explict extension so this breaks for our local package
  output. A bundler is needed and this is what the CLI will do for SSR
  as well.

* We want the Angular linked ESM bundles for framework packages as these
  are only partially compiled. This is not possible to do without
  modifiyng the node modules / or using a bundler that in-memory
  modifies the resolved framework packages (like the CLI does with its
  webpack plugins).

Author: devversion

src/universal-app/BUILD.bazel

@@ -4,6 +4,8 @@ load("//src/cdk-experimental:config.bzl", "CDK_EXPERIMENTAL_TARGETS")
 load("//src/material:config.bzl", "MATERIAL_TARGETS")
 load("//src/material-experimental:config.bzl", "MATERIAL_EXPERIMENTAL_TARGETS")
 load("//tools:defaults.bzl", "ng_module", "sass_binary", "ts_library")
+load("//tools/esbuild:index.bzl", "esbuild")
+load("//tools/angular:index.bzl", "LINKER_PROCESSED_FW_PACKAGES")
 
 package(default_visibility = ["//visibility:public"])
 
@@ -33,6 +35,7 @@ ts_library(
     deps = [
         ":kitchen-sink",
         "@npm//@angular/platform-server",
+        "@npm//@bazel/runfiles",
         "@npm//@types/node",
         "@npm//reflect-metadata",
         "@npm//zone.js",
@@ -53,14 +56,28 @@ sass_binary(
     ],
 )
 
+esbuild(
+    name = "server_bundle",
+    entry_point = ":prerender.ts",
+    platform = "node",
+    # We cannot use `ES2017` or higher as that would result in `async/await` not being downleveled.
+    # ZoneJS needs to be able to intercept these as otherwise change detection would not work properly.
+    target = "es2016",
+    # Note: We add all linker-processed FW packages as dependencies here so that ESBuild will
+    # map all framework packages to their linker-processed bundles from `tools/angular`.
+    deps = LINKER_PROCESSED_FW_PACKAGES + [
+        ":server",
+    ],
+)
+
 nodejs_test(
     name = "server_test",
     data = [
         "index.html",
-        ":server",
+        ":server_bundle",
         ":theme_scss",
     ],
-    entry_point = ":prerender.ts",
+    entry_point = ":server_bundle.js",
     templated_args = [
         # TODO(josephperrott): update dependency usages to no longer need bazel patch module resolver
         # See: https://github.com/bazelbuild/rules_nodejs/wiki#--bazel_patch_module_resolver-now-defaults-to-false-2324

src/universal-app/prerender.ts

@@ -1,20 +1,21 @@
 import 'reflect-metadata';
 import 'zone.js';
 
-import {renderModuleFactory} from '@angular/platform-server';
+import {renderModule} from '@angular/platform-server';
 import {readFileSync, writeFileSync} from 'fs';
 import {join} from 'path';
+import {runfiles} from '@bazel/runfiles';
 
-import {KitchenSinkRootServerModuleNgFactory} from './kitchen-sink-root.ngfactory';
+import {KitchenSinkRootServerModule} from './kitchen-sink-root';
 
 // Do not enable production mode, because otherwise the `MatCommonModule` won't execute
 // the browser related checks that could cause NodeJS issues.
 
 // Resolve the path to the "index.html" through Bazel runfile resolution.
-const indexHtmlPath = require.resolve('./index.html');
+const indexHtmlPath = runfiles.resolvePackageRelative('./index.html');
 
-const result = renderModuleFactory(
-    KitchenSinkRootServerModuleNgFactory, {document: readFileSync(indexHtmlPath, 'utf-8')});
+const result = renderModule(
+    KitchenSinkRootServerModule, {document: readFileSync(indexHtmlPath, 'utf-8')});
 const outDir = process.env.TEST_UNDECLARED_OUTPUTS_DIR as string;
 
 result