This was brought up here #5578 (comment),

our error handler implementation was too naive, and our tests not ideal - the tests only checked that stuff is sent to sentry (which it was!) but not that the page otherwise worked.

Now, I updated the test to ensure this works as expected.

With this PR, the signature for Sentry.setupNestErrorHandler() changes ( breaking change, but sadly required at this point). You have to pass in an exception filter, which we'll extend to also send exceptions to Sentry:

import { BaseExceptionFilter, HttpAdapterHost } from '@nestjs/core';

const { httpAdapter } = app1.get(HttpAdapterHost);
Sentry.setupNestErrorHandler(app1, new BaseExceptionFilter(httpAdapter));

This is a bit more involved, but also allows you to use a custom filter if needed (we can extend any exception filter).