-
-
Notifications
You must be signed in to change notification settings - Fork 9.1k
feat: Optimize live bindings in export declarations (#18494) #19221
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
base: main
Are you sure you want to change the base?
feat: Optimize live bindings in export declarations (#18494) #19221
Conversation
- Optimized live bindings processing to reduce overhead. - Ensured correct hook calls and traversal logic. Fixes webpack#18494
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
@bworline do you want to check over this also? |
@Vansh5632 please review the test failures and snapshot failures. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove unrelated changes and please provide perf benches
@TheLarkInn i am not able to understand the reason behind basic test failing can you give me little bit guidance it will be really grateful |
There are two problems:
|
Super excited about this change and the perf benefits. However, it's difficult to the see the results of this change. Can you show a before and after of webpack generated code, illustrating where the optimization takes place for exports that are not live and those that remain live because of a reference? |
@TheLarkInn can you re-open the underlying issue? It got auto-closed. |
@bworline Done |
Optimized live bindings processing to reduce overhead
Fixes #18494
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
What needs to be documented once your changes are merged?