Hi, I noticed that I seem to be unable to resolve sourcemaps in Node. Here is a full repro with repro steps.
Notice that, in my repro web app, Chrome is able to parse the stacktrace for script.min.js (source: script.js), so the sourcemap seems to be configured correctly:
Yet, in Node.js, when I run:
const stacktrace = "Error\n at http://localhost:3000/script.min.js:1:29"
console.log(new Stacktracey(stacktrace).withSources().asTable())
The output is:
Note that it says script.min.js, not script.js.
I believe I've tracked it down to these lines of code:
|
resolve (nodeRequire ('fs').readFileSync (path, { encoding: 'utf8' })) |
|
nodeRequire ('fs').readFile (path, { encoding: 'utf8' }, (e, x) => { |
Note that, in the browser version of the code, it does an XHR to fetch the path – i.e. it assumes it's a URL, not a filepath. But in Node, it assumes it's a filepath. So we get a "no such file or directory" error:
It seems to me that the Node code should be making an HTTP request rather than doing fs.readFile / fs.readFileSync, similar to what it does in the browser.
Hi, I noticed that I seem to be unable to resolve sourcemaps in Node. Here is a full repro with repro steps.
Notice that, in my repro web app, Chrome is able to parse the stacktrace for
script.min.js(source:script.js), so the sourcemap seems to be configured correctly:Yet, in Node.js, when I run:
The output is:
Note that it says
script.min.js, notscript.js.I believe I've tracked it down to these lines of code:
get-source/get-source.js
Line 146 in 02d7eec
get-source/get-source.js
Line 169 in 02d7eec
Note that, in the browser version of the code, it does an XHR to fetch the
path– i.e. it assumes it's a URL, not a filepath. But in Node, it assumes it's a filepath. So we get a "no such file or directory" error:It seems to me that the Node code should be making an HTTP request rather than doing
fs.readFile/fs.readFileSync, similar to what it does in the browser.