Describe the feature
Node.js stack trace lines are of the form at Object.method (/path/to/file.js:12:34). The contents extracted from the parentheses works as a clickable file location on its own, thanks to #22559, but within the parentheses it is not recognized so Node.js stack trace file locations remain unclickable. It would be nice if it could recognize those to make the file paths clickable.
A full error trace looks something like:
Error: my message
at Object.method (/path/to/file.js:12:34)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async Test.run (node:internal/test_runner/test:935:9)
at async startSubtestAfterBootstrap (node:internal/test_runner/harness:296:3)
The node: prefixed paths might also be nice to support by doing a jump to definition or something like that, but the local file paths are almost there for support, just need recognition of the parentheses wrap.
Describe the feature
Node.js stack trace lines are of the form
at Object.method (/path/to/file.js:12:34). The contents extracted from the parentheses works as a clickable file location on its own, thanks to #22559, but within the parentheses it is not recognized so Node.js stack trace file locations remain unclickable. It would be nice if it could recognize those to make the file paths clickable.A full error trace looks something like:
The
node:prefixed paths might also be nice to support by doing a jump to definition or something like that, but the local file paths are almost there for support, just need recognition of the parentheses wrap.