-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
fix(node): handle offshoot promise rejections #10454
Conversation
🦋 Changeset detectedLatest commit: 328cf34 The changes in this PR will be included in the next version bump. 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 |
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.
Still have a little concern of handling unhandledRejection
for users by default, but I think it's worth trying it out.
That's fair. I think it makes sense for the adapter to do it because there is no natural place for the developer to add the listener - api route top-level, middleware top-level? |
* fix(node): handle offshoot promise rejections * add test * add changeset * Update packages/integrations/node/test/errors.test.js
* fix(node): handle offshoot promise rejections * add test * add changeset * Update packages/integrations/node/test/errors.test.js
Changes
Testing
Docs