datadog-ci sourcemaps find locates local maps by debug ID
Introduced 2026-09-11 · score 0.99
HOW TO USE IT
When a sourcemap is missing from the Datadog UI, locate local `*.js.map` files by top-level `debug_id` or find maps without that field. Run `datadog-ci sourcemaps find` with the build directory and the appropriate query flag; it only inspects local files.
datadog-ci sourcemaps find ./build --debug-id 12345678-1234-1234-1234-123456789abcdatadog-ci sourcemaps find ./build --missing-debug-idWHY THIS HELPS
Troubleshoot a sourcemap missing from the Datadog UI by locating matching artifacts in a local build directory.
REQUIREMENTS AND LIMITATIONS
- Version: v5.24.0
- directory (required): Directory to scan recursively for `*.js.map` files.
- --debug-id <uuid> (required): Selects sourcemaps with the specified top-level `debug_id`; use this query or `--missing-debug-id`.
- --missing-debug-id (required): Selects sourcemaps without a top-level `debug_id`; use this query or `--debug-id`.
- --json: Enables machine-readable output.
- --max-concurrency: Controls concurrent sourcemap inspection.
- The command scans `*.js.map` files recursively and reports matching sourcemap paths.
- It only examines local files and does not verify whether Datadog received an artifact.
- It does not inspect minified JavaScript bundles or compare bundle and sourcemap IDs.
FIRST-PARTY EVIDENCE
- https://github.com/DataDog/datadog-ci/releases/tag/v5.24.0
- https://github.com/DataDog/datadog-ci/pull/2471
- https://github.com/DataDog/datadog-ci/blob/v5.24.0/packages/base/src/commands/sourcemaps/README.md
Check the installed version and the source before using it. Entry JSON