Jest test logging and CI/CD deployment diagnostics: visibility of console.error under silent reporters

Goal: ensure that diagnostic console.error and console.warn messages emitted by Jest tests are visible in CI/CD deployment logs when the test run is executed with a silent reporter or through a CI‑integrated test runner that may suppress output.

Constraints: Jest writes these messages to stderr by default, but the silent reporter can hide them, and it is unclear whether CI systems still capture the stderr stream or if the messages are lost, creating uncertainty about the source of failures.

Does Jest’s silent reporter still forward console.error and console.warn to stderr for CI capture? If not, what configuration or flag can guarantee their visibility without switching to a verbose reporter? How does this behavior differ when Jest is invoked through tools like Create React App, Nx, or Vue CLI?