Skip to content

perf(@ngtools/webpack): avoid full compiler lazy route analysis on JIT rebuilds #20237

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
Mar 11, 2021

Conversation

clydin
Copy link
Member

@clydin clydin commented Mar 11, 2021

The deprecated lazy route string form requires code analysis prior to each build to locate any lazy routes and connect them with Webpack.
This change uses the previous fast but less accurate AST based lazy route discovery for JIT rebuilds. The first build will still perform a full Angular compiler analysis to ensure an accurate list of all initial deprecated string form lazy routes.

@clydin clydin added the target: patch This PR is targeted for the next patch release label Mar 11, 2021
@google-cla google-cla bot added the cla: yes label Mar 11, 2021
…T rebuilds

The deprecated lazy route string form requires code analysis prior to each build to locate any lazy routes and connect them with Webpack.
This change uses the previous fast but less accurate AST based lazy route discovery for JIT rebuilds. The first build will still perform a full Angular compiler analysis to ensure an accurate list of all initial deprecated string form lazy routes.
@clydin clydin force-pushed the webpack-plugin/lazy-route-perf branch from 8998c3d to afced59 Compare March 11, 2021 11:13
@alan-agius4 alan-agius4 merged commit ffbefc9 into angular:11.2.x Mar 11, 2021
@clydin clydin deleted the webpack-plugin/lazy-route-perf branch March 11, 2021 12:07
Comment on lines +579 to +580
if (this.watchMode) {
this.ngtscNextProgram = angularProgram;
Copy link
Member

Choose a reason for hiding this comment

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

Should this be dropped now?

@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 Apr 11, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants