Skip to content
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

fix(@ngtools/webpack): use correct Webpack asset stage in resource loader #20420

Merged
merged 1 commit into from Mar 31, 2021

Conversation

clydin
Copy link
Member

@clydin clydin commented Mar 31, 2021

The asset extraction within the Angular compiler plugin resource loader needs to occur at the end of the Webpack asset processing pipeline. This ensures that all analysis and preprocessing of the asset have been performed before the resource asset is extracted from the Webpack child compilation.

…ader

The asset extraction within the Angular compiler plugin resource loader needs to occur at the end of the Webpack asset processing pipeline. This ensures that all analysis and preprocessing of the asset have been performed before the resource asset is extracted from the Webpack child compilation.
@clydin clydin added the target: major This PR is targeted for the next major release label Mar 31, 2021
@google-cla google-cla bot added the cla: yes label Mar 31, 2021
@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Mar 31, 2021
@filipesilva filipesilva merged commit 430ee44 into angular:master Mar 31, 2021
@clydin clydin deleted the webpack5/resource-loader-phase branch March 31, 2021 16:12
@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 May 1, 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: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants