You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
% node 🍋.mjs
file:///path/to/%F0%9F%8D%8B.mjs:1
throw new Error('🍋')
^
Error: 🍋
at file:///path/to/%F0%9F%8D%8B.mjs:1:7
at ModuleJob.run (node:internal/modules/esm/module_job:218:25)
at async ModuleLoader.import (node:internal/modules/esm/loader:329:24)
at async loadESM (node:internal/process/esm_loader:28:7)
at async handleMainPromise (node:internal/modules/run_main:113:12)
context
context in denoland/deno#23200 (comment) the section of
handle runtime behaviour
and denoland/deno#23200 (comment)
overview
spec
It seems that there is no specification for
Error.stack
today, and it is implementation-defined behaviour by browser engines.example to reproduce
Here is an example code to show stack trace, and runs it on modern browsers.
browser result
Google Chrome(122.0.6261.112)
I think that the stack trace implementation is located as follows.
Firefox(117.0)
Safari(17.3.1)
non-browser result
Node.js(20.12.0)
related issues
denoland/deno#18983
The text was updated successfully, but these errors were encountered: