build(devtools): target es2020 explicitly

We do this because of a bug caused by evanw/esbuild#2950 and a recent change to how angular static properties are attached to class constructors. Targeting esnext or es2022 will cause the static initializer blocks that attach these static properties on class constructors to reference a class constructor variable that they do not have access to. Because of this we explicitly target es2020 in our Angular DevTools builds.
AleksanderBodurri · May 1, 2023 · 3281967 · 3281967
1 parent df30710
commit 3281967
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/devtools/projects/shell-browser/src/BUILD.bazel b/devtools/projects/shell-browser/src/BUILD.bazel
@@ -64,7 +64,7 @@ esbuild(
     minify = True,
     platform = "browser",
     splitting = False,
-    target = "esnext",
+    target = "es2020",
     deps = LINKER_PROCESSED_FW_PACKAGES + [":src"],
 )
 
@@ -76,7 +76,7 @@ esbuild(
     minify = True,
     platform = "browser",
     splitting = False,
-    target = "esnext",
+    target = "es2020",
     deps = [":devtools"],
 )
 

diff --git a/devtools/src/BUILD.bazel b/devtools/src/BUILD.bazel
@@ -45,7 +45,7 @@ esbuild(
     entry_points = [":main.ts"],
     platform = "browser",
     splitting = True,
-    target = "es2016",
+    target = "es2020",
     deps = LINKER_PROCESSED_FW_PACKAGES + [":demo"],
 )