Which @angular/* package(s) are the source of the bug?

common

Is this a regression?

No

Description

When an HTTP request is initiated after the Angular injector has been destroyed (e.g. during SSR teardown, or via a third-party SDK that captures HttpClient and fires async callbacks), Angular throws NG0205: Injector has already been destroyed.
While this error is intentional, it is unactionable in production because:

• The stack trace is fully minified — no readable symbols or context
• The request URL is never included in the error, which is the one piece of runtime information that would identify the culprit
• It is impossible to determine from the trace alone whether the call originated from your own code or a third-party dependency

This makes the error controversial in production monitoring tools (Rollbar, Sentry, Datadog) — you know something went wrong, but you cannot determine what, where, or whether it caused actual data loss.

Please provide a link to a minimal reproduction of the bug

https://github.com/arturovt/ng-request-after-injector-destroyed

Please provide the exception or error you saw

Please provide the environment you discovered this bug in (run ng version)

Anything else?

No response