fix: event listener error handling #586
Merged
+70
−14
Conversation
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
🦋 Changeset detectedLatest commit: bf5c8e5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
fraxken
requested changes
Dec 15, 2025
ErwanRaulo
force-pushed
the
fix/payload-error-handling
branch
3 times, most recently
from
fed9bd3 to
35c256c
Compare
ErwanRaulo
commented
Dec 22, 2025
ErwanRaulo
force-pushed
the
fix/payload-error-handling
branch
2 times, most recently
from
cb911fc to
51f9b9a
Compare
ErwanRaulo
force-pushed
the
fix/payload-error-handling
branch
from
51f9b9a to
bf5c8e5
Compare
fraxken
approved these changes
Dec 24, 2025
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.
context:
event target dispatch erros through process.nextTick, so the engine treats as an asynchronous operation that leads to unwanted warning during unit tests by test runner.
fix:
try catch error and log it at payload level