Upload source maps with CLI

Install posthog-cli:

npm install -g @posthog/cli

To authenticate the CLI, you can call the login command and follow the instructions:

posthog-cli login

If you are using the CLI in a CI/CD environment such as GitHub Actions, you can set environment variables to authenticate:

Use the --host option in subsequent commands to specify a different PostHog instance / or region. For EU users:

posthog-cli --host https://eu.posthog.com [CMD]

Once you've built your application and have bundled assets, inject the context required by PostHog to associate the maps with the served code.

# Inject release and chunk metadata into sourcemaps
posthog-cli sourcemap inject --directory ./path/to/assets --project my-app --version 1.2.3

The CLI will create or reuse the release for the detected or supplied project and version. The CLI will try to detect project and version information, but you can set them explicitly with --project and --version. We recommend setting the project, and letting the CLI detect the version, if your project is continuously deployed (the version will be the git commit hash at build time).

You can verify that the metadata has been injected by checking for the //# chunkId=... comment in the minified code.

You will then need to upload the modified assets to PostHog.

# Upload injected sourcemaps to their release
posthog-cli sourcemap upload --directory ./path/to/assets

The CLI reuses the release stored during injection, so you don't need to pass --project or --version again.

💡 Tip: You can use --delete-after option to clean up sourcemaps after uploading them.

You must serve the injected assets in deployed production app. The injected metadata is used during error capture to identify the correct source map to use.

If you serve a copy of the bundled assets as they were prior to running posthog-cli sourcemap inject, we won't be able to use the uploaded sourcemap to unminify or demangle your stack traces.

Confirm that source maps are successfully uploaded to PostHog.