fix: sourceTypes of asset module when lazy compilation#19539
Merged
alexander-akait merged 1 commit intowebpack:mainfrom May 20, 2025
hai-x:fix-asset-type
Merged
fix: sourceTypes of asset module when lazy compilation#19539alexander-akait merged 1 commit intowebpack:mainfrom hai-x:fix-asset-type
alexander-akait merged 1 commit intowebpack:mainfrom
hai-x:fix-asset-type
Conversation
Member
Author
|
In To ensure robust module connections, I propose defaulting to JS_TYPES or JS_AND_ASSET_TYPES. |
CodSpeed Performance ReportMerging #19539 will degrade performances by 81.73%Comparing Summary
Benchmarks breakdown
|
alexander-akait
approved these changes
May 20, 2025
3ru
pushed a commit
to 3ru/webpack
that referenced
this pull request
Jul 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Fixes #19532.
Did you add tests for your changes?
Yes
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
No