You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build: remove flat module bundle workaround from view engine (angular#23826)
Removes a past flat module bundle workaround that was needed when we
still shipped release packages with View Engine. The Angular compiler
picks the `index.ts` files as entry-point for the flat module bundles
(this whole flat module construct could be removed in the future anyway).
This was problematic because to avoid conflicts, the flat module out
file name was set to something unique that does not conflict with the
index file. The metadata JSON files for the `ng_module` targets (within our repo)
then did not reside next to the `index` files, but rather next to the
auto-generated flat module bundle. This broke the generation of
`defineInjectable` (which was used in VE as well) calls.
We worked around this in the past by patching the Angular compiler to
pick the public API file instead as entry-point; allowing us to let
the Angular compiler generate metadata and the bundle as `index.js` and
`index.metadata.json` (ensuring the release output worked then).
All of this is no longer needed with Ivy, so we can remove the
workaround and unblock angular/angular#43932
(which fails due to us patching some files in the compiler-cli package)
0 commit comments