AleksanderBodurri aee526a08b build(devtools): make sure linker runs on fesm2022 bundles (#50086) ... Since DevTools' Angular framework dependencies are built from local files, they are always up to date. [Recently](https://github.com/angular/angular/pull/49332) these dependencies started being published as fesm2022 instead of fesm2020. We also have an Angular dependency `ngx-flamegraph` that was built and published as fesm2020. The easiest fix to make sure all of our Angular based dependencies are processed by the linker would be to update the filterPaths field in that file from `/fesm2020/` to `/fesm2020|fesm2022/`. When v16 releases, we can update ngx-flamegraph and publish it with the new APF, letting us change filterPaths to just `/fesm2022/`. PR Close #50086		2023-05-09 14:41:48 -07:00
..
BUILD.bazel	refactor: simplify devtools setup given recent ESM changes (#48521)	2022-12-19 19:50:44 +00:00
esbuild-base.config.mjs	build(devtools): make sure linker runs on fesm2022 bundles (#50086)	2023-05-09 14:41:48 -07:00
esbuild-esm-prod.config.mjs	build(devtools): fix issue where esbuild configs were not being set properly in DevTools (#48762)	2023-01-18 10:45:13 -08:00
esbuild-esm.config.mjs	build(devtools): fix issue where esbuild configs were not being set properly in DevTools (#48762)	2023-01-18 10:45:13 -08:00
esbuild-iife.config.mjs	build(devtools): fix issue where esbuild configs were not being set properly in DevTools (#48762)	2023-01-18 10:45:13 -08:00
esbuild-spec.config.mjs	build(devtools): fix issue where esbuild configs were not being set properly in DevTools (#48762)	2023-01-18 10:45:13 -08:00
index.bzl	build: update cross-repo angular dependencies (#49887)	2023-04-17 15:46:39 +00:00