console.warn logged as error | want help with fixing this bug

[EllisCallaghan]

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.

Describe the bug

supabase/supabase#22395

this bug was posted in the supabase main repo and I have been trying to fix it, it seems like the error is not from that repo but in this one, I want to try and fix it, can you guys point me to where the logging for edge functions is written so I can try and fix it?

To Reproduce

open supabase dashboard and go to edge function logs

Expected behavior

console.warn displays a yellow WARNING log

Screenshots

[laktek]

Thanks for reporting this @EllisCallaghan. Technically, not an edge runtime issue but I'll leave this issue open till we fix it in the Supabase Dashboard.

[EllisCallaghan]

oh ok cool, just curious where is the code for this? how does the edge functions log work?

[EllisCallaghan]

@laktek to word that more precisely how does supabase generate data for console logs in edge functions? Thanks!

[laktek]

@EllisCallaghan In the hosted platform, an internal service (closed source) is responsible for piping the edge function logs to the destination. So unfortunately, someone from the internal Supabase team needs to fix it.

[EllisCallaghan]

ok cool thanks man

[jareddr]

Just want to +1 this. Having the same issue. Hoping to have my logging broken up by category so it's easier to track down problems.

[michaelmagan]

Yeah having the same issue :)

[jareddr]

Very related to this, the console.info command filters to logs rather than info on the supabase edge function log viewer.

So the mapping I've observed so far is:

javascript function => supabase edge function log severity
console.log => log
console.info => log
console.error => error
console.warn => error