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
{{ message }}
Repository navigation
ngc: support third-party codegen on install (ngc --init) #18810
Angular libraries ship without codegen (eg. ngfactory.js, ngsummary.js) so users need to compile these with ngc.
Right now this work is done for every run of ngc even though the libraries haven't changed. Doing this as an npm postinstall step would save time. Also it's needed for bazel.
Reacted by Fabian Wiles, Adrian Fedoreanu, Jared Neil, Kliment, Paul Gschwendtner, Elvis Begovic, Rasmus Hansen, Tine Jozelj and Michael Prentice
I added this to the linker project as somewhat related, but upon further thought it may not be. Nowadays ngcc is precompiling libraries during postinstall, which is what is being requested in this issue. However, ngcc is an interim solution for compatibility, which the linker being the replacement. We are not currently planning to support a caching layer for the linker.
not something we will support in View Engine, for reasons of deprecation
the ultimate state will be that all libraries are shipped in partially compiled format and finalized with the Angular Linker, which is implemented as a Babel plugin. Babel supports caching, so a dedicated build author could implement similar functionality.
Activity
chuckjaz commentedon Aug 22, 2017
Blocking until runtime localization is available which then will generate a locale independent factories in the prepare step.
Workaround for missing ngfactory, ngsummary... in angular packages
chore: add workaround for ABC
LinboLen commentedon Mar 26, 2019
it works, but it takes me lots of time to figure it out.
thesayyn commentedon Apr 4, 2019
Any update on this ?
We need to compile @FortAwesome with ngc
JoostK commentedon Nov 25, 2020
I added this to the linker project as somewhat related, but upon further thought it may not be. Nowadays ngcc is precompiling libraries during postinstall, which is what is being requested in this issue. However, ngcc is an interim solution for compatibility, which the linker being the replacement. We are not currently planning to support a caching layer for the linker.
alxhub commentedon May 3, 2021
Closing as this is:
angular-automatic-lock-bot commentedon Jun 3, 2021
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.