[Bug] Show Request reference in script stacktraces

[Xarno]

Description

If a scrip errors you get currently this:

at new AsyncFunction () at self.onmessage ([worker eval]:114:20) at MessagePort. ([worker eval]:3:82) at [nodejs.internal.kHybridDispatch] (node:internal/event_target:845:20) at MessagePort. (node:internal/per_context/messageport:23:28)

Steps to Reproduce

Have a broken pre or post request script

Expected Behavior

Add the request name and the origin (per-request, post-request, maybe others?) to the stack print output.
Like this:

at pre request (line number possible?)
at CleanupDeleteCalendarEntryNotificationsUser1 
at new AsyncFunction (<anonymous>)
at self.onmessage ([worker eval]:114:20)
at MessagePort.<anonymous> ([worker eval]:3:82)
at [nodejs.internal.kHybridDispatch] (node:internal/event_target:845:20)
at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)

Environment

Mac,
Voiden 2.3. beta

[suhailopensource]

@Xarno let me try reproducing this .

[davinder-sudo]

Hi @suhailopensource, just checking in—were you able to reproduce this issue?

[suhailopensource]

Hi @suhailopensource, just checking in—were you able to reproduce this issue?

not yet im trying ill finalize by today.

[Xarno]

This level of broken script will do

Script execution failed: SyntaxError: await is only valid in async functions and the top level bodies of modules
at new AsyncFunction ()
at self.onmessage ([worker eval]:114:20)
at MessagePort. ([worker eval]:3:82)
at [nodejs.internal.kHybridDispatch] (node:internal/event_target:845:20)
at MessagePort. (node:internal/per_context/messageport:23:28)

[suhailopensource]

Reproduced ✅ @Xarno

function getToken() {
  const res = await fetch("https://api.example.com/token");
  return res.json();
}

voiden.variables.set("token", getToken());
Gives byte-for-byte your output (event_target:843 vs 845 is just my Node v22.22.2):

Script execution failed: SyntaxError: await is only valid in async functions and the top level bodies of modules
    at new AsyncFunction (<anonymous>)
    at self.onmessage ([worker eval]:114:20)
    at MessagePort.<anonymous> ([worker eval]:3:82)
    ...

Root cause
The trace comes from VoidenHQ/plugin-voiden-scripting (v1.1.6), not this repo — here it's only piped through apps/electron/src/main/ipc/nodeScript.ts.

scriptEngine.ts:151 — the script is compiled via new AsyncFunction(...), so a syntax error throws at compile time and the stack has no user-code frame at all, only engine wrapper frames.
scriptEngine.ts:155 — the worker posts back error.stack verbatim.
Notably, pipelineHooks.ts:58 already defines formatScriptRuntimeError() — it extracts line/column and even compensates for the AsyncFunction offset — but it's never called. The raw stack is assigned straight through at pipelineHooks.ts:203 (pre) and :300 (post). So much of this issue is already written and just unwired.