Transformers Regression and Swallowed console.errors

[CyrusNuevoDia]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Bugs and steps to reproduce

1. Using code based on the gte-small deno example, my application was working fine.
2. Out of nowhere, it started failing one day. Unfortunately, the uncaught errors were not logged, despite the docs saying so
3. I tried wrapping my endpoint in a try/catch that console.error'd the message and that didn't show up in the logs either
4. I added console.log's in between every failable call and finally discovered that the issue was with the transformer pipe call
   
5. reverted my code to that from 2 months ago that was closer to the gte-small deno example (from 1) and that still didn't work and was failing on the pipe call as well as failing to log console.errors

Expected behavior

1. uncaught exceptions are console.error'd in the logging UI
2. transformers package support doesn't regress

Screenshots & Trace

Here is a screenshot of the trace ID from the supabase dashboard. This function should have ran the transformers pipeline but instead boots, listens, and exits without running any code.