feat(compiler-cli): JIT compilation of component declarations #40127
Conversation
557e067
to
e685467
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the |
Another marvellous PR @JoostK - just a couple of nits and bike-sheds.
reviewed-for: fw-core
Reviewed-for: dev-infra
L even better TM
The `render3` test targets are currently also executed for ViewEngine builds, even though the `render3` infrastructure only concerns Ivy infrastructure. This commit tags the test targets as ivy-only to disable those tests for View Engine.
The `ɵɵngDeclareComponent` calls are designed to be translated to fully AOT compiled code during a build transform, but in cases this is not done it is still possible to compile the declaration object in the browser using the JIT compiler. This commit adds a runtime implementation of `ɵɵngDeclareComponent` which invokes the JIT compiler using the declaration object, such that a compiled component definition is made available to the Ivy runtime.
The `ɵɵngDeclareComponent` calls are designed to be translated to fully AOT compiled code during a build transform, but in cases this is not done it is still possible to compile the declaration object in the browser using the JIT compiler. This commit adds a runtime implementation of `ɵɵngDeclareComponent` which invokes the JIT compiler using the declaration object, such that a compiled component definition is made available to the Ivy runtime. PR Close #40127
…ction name The "monitoring" workflow is has been failing since angular#40127 was merged, due to a Saucelabs test failure in Internet Explorer 11. The issue is with the test's expectation which does not account for Ivy instruction invocations to use "anonymous" instead of the instruction's function name. This commit changes the test expectation to also accept "anonymous", which was already the case for similar expectations.
…ction name The "monitoring" workflow has been failing since angular#40127 was merged, due to a Saucelabs test failure in Internet Explorer 11. The issue is with the test's expectation which does not account for Ivy instruction invocations to use "anonymous" instead of the instruction's function name. This commit changes the test expectation to also accept "anonymous", which was already the case for similar expectations.
…ction name (#40342) The "monitoring" workflow has been failing since #40127 was merged, due to a Saucelabs test failure in Internet Explorer 11. The issue is with the test's expectation which does not account for Ivy instruction invocations to use "anonymous" instead of the instruction's function name. This commit changes the test expectation to also accept "anonymous", which was already the case for similar expectations. PR Close #40342
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |


The
ɵɵngDeclareComponentcalls are designed to be translated to fullyAOT compiled code during a build transform, but in cases this is not
done it is still possible to compile the declaration object in the
browser using the JIT compiler. This commit adds a runtime
implementation of
ɵɵngDeclareComponentwhich invokes the JIT compilerusing the declaration object, such that a compiled component definition
is made available to the Ivy runtime.
The text was updated successfully, but these errors were encountered: