fix: initialize lazy compilation backend earlier#9342
Merged
Conversation
✅ Deploy Preview for rspack canceled.
|
CodSpeed Performance ReportMerging #9342 will not alter performanceComparing 🎉 Hooray!
|
JSerFeng
approved these changes
Feb 17, 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
2 participants
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.
Summary
The lazy compilation backend needs to listen to the server's "listening" event, and we need to ensure that the backend is initialized before the
listen()call.There are two cases:
backend.server, thelisten()method is called by the user, which is usually earlier thancompiler.hooks.beforeCompilehook.This PR moves up the timing of the backend initialization to avoid the second case.
Checklist