---
title: "ezgh obs sourcemaps"
description: "Source maps: debug IDs, and uploads that symbolicate browser errors."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ezghcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ezgh obs sourcemaps

{/* Generated by ezgh-cli's internal/tools/clidocs from the ezgh command tree. Don't edit: change the command's help in ezgh-cli and regenerate. */}

```sh
ezgh obs sourcemaps <command>
```

Source maps turn the minified stack traces browsers send into your original files, lines and function names. Each emitted JS file and its map share a debug ID: `inject` writes it into your build output (the @ezghcloud/rum-build bundler plugin does the same at build time), and `upload` registers the maps and JS files under an application's release. Errors whose script has a registered debug ID are symbolicated as they arrive; source maps are never served to browsers.

Uploads are content-addressed chunks, so an interrupted upload resumes by running the same command again. Source maps are in a project (`--project`, `EZGH_PROJECT` or the profile's), up to 10 GiB, and are deleted 90 days after an error last used them.

Part of [`ezgh obs`](/cli/reference/obs).

## Flags

This command also takes the [global flags](/cli/reference#global-flags).

## Subcommands

| Command | Description |
| --- | --- |
| [`ezgh obs sourcemaps delete`](/cli/reference/obs-sourcemaps-delete) | Delete a release's source maps |
| [`ezgh obs sourcemaps inject`](/cli/reference/obs-sourcemaps-inject) | Give each JS file in a build and its source map a debug ID |
| [`ezgh obs sourcemaps list`](/cli/reference/obs-sourcemaps-list) | List the releases with source maps, or one release's files |
| [`ezgh obs sourcemaps upload`](/cli/reference/obs-sourcemaps-upload) | Upload a build's source maps and JS files for a release |

Source: https://docs.ezghcloud.com/cli/reference/obs-sourcemaps/index.mdx
