sourcemapped-traces

sourcemapped-traces is a utility to resolve javascript sourcemaps in:

- Chromium event traces taken with the performance tab in the chrome inspector
- Chromium allocation sampling traces taken with the memory tab in the chrome inspector
- Node inspector traces (cpu or heap) taken with the node:inspector API. You can see an example in this repo.

!Screenshot showing the non-resolved trace and resolved trace in the VSCode flamechart vizualizer

Using the cli tool

``
npx sourcemapped-traces cpu CPUPROFILE_FILE SOURCEMAP_FILE [DECODED_OUTPUT_FILE]
npx sourcemapped-traces heap HEAPPROFILE_FILE SOURCEMAP_FILE [DECODED_OUTPUT_FILE]
`

For instance, you can try in this repo in the example/ directory:

`sh
cd ./example
npm install
npm run build
npm start

npx sourcemapped-traces cpu ./profile.cpuprofile ./output.js.map ./profile.mapped.cpuprofile
npx sourcemapped-traces heap ./profile.heapprofile ./output.js.map ./profile.mapped.heapprofile
`

In most cases, this should properly resolve your sources and you can continue
your performance analysis adventure.

Sometimes, however, you will see some source misses that are significant for you:

`js
Input misses Set(2) {
'http://example.com/foo.js',
'http://example.com/bar.js'
}
`

In that case, you might want to create your own decoding tool using the API...

Using the API

The CLI tool can be quite blunt and will not handle very well situations where
you have multiple output files to map.

In this case, we would recommend building up your own cli using the API:

`js
import { decodeCpuProfile } from "sourcemapped-traces";
import { readFile, writeFile } from "node:fs/promises";

const profileJson = JSON.parse(await readFile(process.args[2], "utf8"));
const sourcemaps = {
"http://example.com/foo.js": JSON.parse(
await readFile("./foo.js.map", "utf8")
),
"http://example.com/bar.js": JSON.parse(
await readFile("./bar.js.map", "utf8")
),
};
const { decoded, inputMisses } = await decodeCpuProfile(
profileJson,
sourcemaps
);
console.warn("Input misses", inputMisses);
await writeFile(process.argv[3], JSON.stringify(decoded), "utf8");
`

Both decodeCpuProfile and decodeHeapProfile` have the same signature.