feat: Add pre/post launch hooks to BrowserPool#1879
Merged
vdusek merged 2 commits intoapify:masterfrom May 7, 2026
Merged
Conversation
vdusek
approved these changes
May 7, 2026
Collaborator
vdusek
left a comment
vdusek
left a comment
There was a problem hiding this comment.
I did just minor polishment, otherwise LGTM
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
3 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.
Description
Add two browser launch hooks to
BrowserPoolregistered as decorators:pre_launch_hook- called before a new browser is launched.post_launch_hook- called after a new browser is launched, receives the newly createdBrowserController. If the hook raises, the browser is closed before the error is propagated.Issues
Testing
BrowserPool.