Error stack trace giving incorrect line number (possibly related to async eval?)
In a handler for a Fresh application I noticed that assertion errors were giving the wrong line number. Throwing an error gives a line number of 22 in the attached error message. However, the actual error is being thrown on line 162. deno.jsondeno.json and deno.lockdeno.lock attached. Any idea what might be causing this? Thanks!