Package + Version
Version:
Description
Hi! I'm using Sentry with a Blitzjs stack, which is a mildly abstracted version of Next.js. Generally, the Next.js sentry module works very well, but after 6.14.3, I experienced crashes on any request in prod:
Nov 11 04:11:01 PM Error [ERR_STREAM_WRITE_AFTER_END] [ERR_STREAM_WRITE_AFTER_END]: write after end
Nov 11 04:11:01 PM at writeAfterEnd (_http_outgoing.js:694:15)
Nov 11 04:11:01 PM at write_ (_http_outgoing.js:706:5)
Nov 11 04:11:01 PM at ServerResponse.write (_http_outgoing.js:687:15)
Nov 11 04:11:01 PM at ServerResponse.write (/opt/render/project/src/node_modules/next/dist/compiled/compression/index.js:1:4006)
Nov 11 04:11:01 PM at Request.ondata (internal/streams/readable.js:745:22)
Nov 11 04:11:01 PM at Request.emit (events.js:376:20)
Nov 11 04:11:01 PM at Request.emit (domain.js:532:15)
Nov 11 04:11:01 PM at addChunk (internal/streams/readable.js:309:12)
Nov 11 04:11:01 PM at readableAddChunk (internal/streams/readable.js:284:9)
Nov 11 04:11:01 PM at Request.Readable.push (internal/streams/readable.js:223:10)
This is noted in the PR itself, and appears to not affect Next.js in some configurations, but clearly affects my relatively vanilla setup of Blitz running on Render (and the bug also appears locally). I'll try to figure out if this is purely a Blitz-level occurrence or something that manifests in Render on serverful non-Lambda environments as well. I've set up the externalResolver option as suggested to avoid the error message that this PR attempts to fix systematically.
Package + Version
@sentry/next-jsVersion:
Description
Hi! I'm using Sentry with a Blitzjs stack, which is a mildly abstracted version of Next.js. Generally, the Next.js sentry module works very well, but after 6.14.3, I experienced crashes on any request in prod:
This is noted in the PR itself, and appears to not affect Next.js in some configurations, but clearly affects my relatively vanilla setup of Blitz running on Render (and the bug also appears locally). I'll try to figure out if this is purely a Blitz-level occurrence or something that manifests in Render on serverful non-Lambda environments as well. I've set up the
externalResolveroption as suggested to avoid the error message that this PR attempts to fix systematically.