Add the ability to apply source maps from the CLI - #6229
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6229 +/- ##
==========================================
- Coverage 83.69% 83.58% -0.12%
==========================================
Files 348 350 +2
Lines 37433 37498 +65
Branches 10514 10539 +25
==========================================
+ Hits 31330 31343 +13
- Misses 5676 5728 +52
Partials 427 427 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
fatadel
left a comment
There was a problem hiding this comment.
Thanks for the work and sorry for the long review! I've left some comments but I think they are mostly minor ones.
| case 'sourcemap-ambiguous': { | ||
| const lines = result.candidates.map(formatSourceEntry); | ||
| return [ | ||
| 'The source map matches more than one source. Re-run with --to <src-N> to pick one:', |
There was a problem hiding this comment.
This is returned for both "matches several" and "matches nothing" leading to:
➜ profiler git:(sourcemap-cli) pq sourcemap apply ~/Downloads/mystery.js.map
The source map matches more than one source. Re-run with --to <src-N> to pick one:
when in reality it does not match any.
There was a problem hiding this comment.
Oh yeah, it looks like this is also an issue in the web frontend. I'll address that as a follow-up.
| return { | ||
| kind: 'inline', | ||
| mediaType: sourceMapURL.slice('data:'.length).split(',', 1)[0], | ||
| byteLength: sourceMapURL.length, |
There was a problem hiding this comment.
Should this probably exclude the prefix length?
There was a problem hiding this comment.
Technically you're right, but I don't think we should do it here. This is already an approximation, so it doesn't have to be strictly accurate.
| if (!existsSync(wasmUrl)) { | ||
| console.error( | ||
| `profiler-cli source map parser not found at ${fileURLToPath(wasmUrl)}.\n` + | ||
| `Without it, 'sourcemap apply' silently applies nothing.\n` + |
There was a problem hiding this comment.
Without it, 'sourcemap apply' fails with a symbolication error.\n would be more correct, because in that case it actually fails.
There was a problem hiding this comment.
It actually doesn't fail and rather fails silently. But I don't think we should care about that case in the runtime of the cli, since it's mostly a packaging thing.
Added a SourceMapRunner type and an optional `run` argument to doSourceMapSymbolication through applySourceMapFile, to make the source map symbolication runner injectable. The default behavior stays as the Web Worker runner, but let's the non-browser callers inject a runner that calls the core logic directly, since the profiler-cli Node daemon has no Workers.
`ApplySourceMapFileResult` only carried the resolved bundle source's filename, which is all the web UI needs. Add the source table index alongside it, so callers that identify sources by index rather than by name can report which source the map landed on. A follow-up uses this to add "sourcemap" commands to profiler-cli, which refers to sources by "src-N" handles.
Lists the bundle sources that carry a `sourceMapURL` and are therefore eligible to have a `.map` applied to them -- the same set the web app's "Apply source map…" picker offers. Each gets a `src-N` handle, which is a direct index into `profile.shared.sources` and so is stable across sessions for the same profile, like `f-N`. Firefox stores an inline map's entire `data:` URL in the source table, so a "URL" can be megabytes of base64. Those are reported by media type and size instead, which keeps the payload out of both the text and `--json` output. The integration fixtures are pre-generated and committed because the profile builders are DOM-coupled and can't run in the node-env test process, so sourcemap-generator.ts regenerates them via a browser-env test. A follow-up adds "sourcemap apply", which consumes these handles.
Brings the web app's "Apply source map…" feature to profiler-cli, reusing the shared `applySourceMapFile` thunk. Since the CLI is one-shot, the web picker becomes a two-step flow: "sourcemap sources" lists the candidates, then "sourcemap apply <path> [--to src-N]" reads the .map on the daemon, auto-matches it to a source (or applies to the source given by --to) and re-symbolicates in place. Ambiguous matches and errors exit non-zero so scripts can branch on them. The daemon has no Web Worker, so it injects a runner that calls the symbolication core directly on the current thread. That core's `source-map` dependency reads its WASM parser from `path.join(__dirname, 'mappings.wasm')` at runtime, and esbuild does not bundle that file, so the build copies it next to the bundle and the publish check now fails if it is missing -- without it, "sourcemap apply" silently applies nothing. `--to` only accepts sources that carry a `sourceMapURL`, the same set the web picker offers. Applying a map to any other source would skip the auto-match step's `no-eligible-sources` guard and then de-minify nothing, which reads as a successful apply.
Adds a SOURCE MAPS section covering the sources -> apply flow and the --to disambiguation step, and lists src-N in the handle reference tables alongside t-N / f-N / c-N / ts-N.
| if (!existsSync(wasmUrl)) { | ||
| console.error( | ||
| `profiler-cli source map parser not found at ${fileURLToPath(wasmUrl)}.\n` + | ||
| `Without it, 'sourcemap apply' silently applies nothing.\n` + |
There was a problem hiding this comment.
It actually doesn't fail and rather fails silently. But I don't think we should care about that case in the runtime of the cli, since it's mostly a packaging thing.
| return { | ||
| kind: 'inline', | ||
| mediaType: sourceMapURL.slice('data:'.length).split(',', 1)[0], | ||
| byteLength: sourceMapURL.length, |
There was a problem hiding this comment.
Technically you're right, but I don't think we should do it here. This is already an approximation, so it doesn't have to be strictly accurate.
| case 'sourcemap-ambiguous': { | ||
| const lines = result.candidates.map(formatSourceEntry); | ||
| return [ | ||
| 'The source map matches more than one source. Re-run with --to <src-N> to pick one:', |
There was a problem hiding this comment.
Oh yeah, it looks like this is also an issue in the web frontend. I'll address that as a follow-up.
Changes: [fatadel] Create the Network track from the timeline-network schema display location (#6224) [Markus Stange] Only call `getRawFrameTableBuilderWithExistingContents` once per symbolication batch. (#6233) [fatadel] Improve discoverability of downloading a local profile (#6216) [Nazım Can Altınova] Handle the cli daemon startup failures more gracefully with better errors (#6241) [Nazım Can Altınova] Add the ability to apply source maps from the CLI (#6229) [Nazım Can Altınova] Handle Text and Log marker payloads with their marker schema (#6247) [Nazım Can Altınova] Bump the Gecko profile version to make sure that the Text and Log marker changes are picked up in the frontends (#6252) [fatadel] Deactivate a menu button as soon as its panel is dismissed (#6251) [Nazım Can Altınova] 🔃 Sync: l10n -> main (August 10, 2026) (#6253) [Nazım Can Altınova] Bump profiler-cli version to 0.8.0 (#6254) And special thanks to our localizers: de: Ger de: Michael Köhler el: George kitsoukakis en-CA: chutten en-CA: Saurabh en-GB: Ian Neal es-CL: ravmn fy-NL, nl: Fjoerfoks fr: Théo Chevalier fy-NL: Fjoerfoks ia: Melo46 it: Francesco Lodolo [:flod] nl: Fjoerfoks ru: michellemelsspam ru: Valery Ledovskoy tr: giray tr: Selim Şumlu zh-TW: Pin-guang Chen
Main | Deploy preview
This fixes #6196.
This PR adds 2 commands to the CLI so we can apply source maps from local files later:
pq sourcemap sourcespq sourcemap applysourcemap sourcesis used for determining which sources we can apply the source maps onto. andsourcemap applyis to apply that source map that we provide as an argument.For example the output of
sourcemap sources:Then
pq sourcemap apply <sourcemap-path>could optionally take--to <src-N>argument.If it's not provided, we try to match the source map given to an existing source, if it matches, great, it's done. If it doesn't match, we show an error saying that the user has to provide the
--to <src-N>by looking at the output ofsourcemap sources. If that argument is provided, we automatically apply to that only.For example:
And then:
Example profile to test:
https://share.firefox.dev/4fIRaUh
And this is the source map for the bundle: index-XVVABR7J.js.map.zip
(note you have to unzip it before using, apparently github doesn't allow uploading .map file extensions, so I had to zip it)