Problem Statement
Stemming from a discussion in discord and subsequent conversations with Vercel:

this can be caused by the throw null throw 0 throw undefined which would cause this line if (err) to not proceed
That’s why we’re stripping the confusing error message we were adding, but what’s your recommendation ?
Solution Brainstorm
Vercel has fixed to remove the unhelpful error in the example repo already
vercel/next.js#36902
we could do a captureMessage
Problem Statement
Stemming from a discussion in discord and subsequent conversations with Vercel:
Solution Brainstorm
Vercel has fixed to remove the unhelpful error in the example repo already
vercel/next.js#36902
we could do a captureMessage