Skip to content

fix(@ngtools/webpack): don't use skipTemplateCodegen to determine if compilation is JIT mode #19953

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 3, 2021
Merged

Conversation

alan-agius4
Copy link
Collaborator

@alan-agius4 alan-agius4 commented Feb 3, 2021

With this change we add a new jitMode option to the ivy AngularWebpackPlugin.
readConfiguration from @angular/compiler-cli will use file configuration options over programmaticly supplied options. By using a separate option the options precedence issue can be avoided.

Closes #19949

@alan-agius4 alan-agius4 added the target: patch This PR is targeted for the next patch release label Feb 3, 2021
@alan-agius4 alan-agius4 requested a review from clydin February 3, 2021 14:32
@google-cla google-cla bot added the cla: yes label Feb 3, 2021
Copy link
Contributor

@petebacondarwin petebacondarwin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SGTM!

@alan-agius4
Copy link
Collaborator Author

test-browsers is flakey

@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Feb 3, 2021
…f compilation is JIT mode

With this change we add a new `jitMode` option to the ivy AngularWebpackPlugin.
`readConfiguration` from `@angular/compiler-cli` will use file configuration options over programmaticly supplied options. By using a separate option the options precedence issue can be avoided.

Closes #19949
@alan-agius4 alan-agius4 merged commit d2ce3e7 into angular:master Feb 3, 2021
@alan-agius4 alan-agius4 deleted the ngtools/jit-mode branch February 3, 2021 19:44
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Component stopped rendering ngFor in Angular 11.1.x (works in 11.0.x)
3 participants