-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
res.once is not a function #4463
Comments
There is a pull request for this |
lobsterkatie
added a commit
that referenced
this issue
Jan 28, 2022
…erver (#4467) In vercel/next.js#32999 (released as part of 12.0.9), Next.js made an internal change, so that it now wraps the raw `http.IncomingMessage` and `http.ServerResponse` objects which get passed to the main server request handler in `NodeNextRequest` and `NodeNextResponse` objects, respectively. We therefore need to unwrap them before we can use them. This does that unwrapping (if necessary; older versions of nextjs still don't need it) and fixes the relevant types. Fixes #4463 Fixes vercel/next.js#33726
Fixed in https://www.npmjs.com/package/@sentry/nextjs/v/6.17.3. If anything else comes up, please let us know! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Package + Version
@sentry/browser
@sentry/node
raven-js
raven-node
(raven for node)Version:
Description
I get the following error whenever I get an error in nextjs (12.0.8)
Code in the file thats causing the error
The text was updated successfully, but these errors were encountered: