rabbit_rabbitR
Deno3mo ago
44 replies
rabbit_rabbit

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.json
and
deno.lock
attached. Any idea what might be causing this? Thanks!


```deno --version
deno 2.3.5 (stable, release, aarch64-apple-darwin)
v8 13.7.152.6-rusty
typescript 5.8.3
image.png
message.txt98.54KB
Was this page helpful?