Upload source maps for web

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]

If you serve minified bundles in production, PostHog requires source maps to generate accurate stack traces. Here are instructions to enable source map generation for popular build tools:

For other build tools, consult their documentation to enable source maps.

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 metadata in files to resolve errors
posthog-cli sourcemap inject --directory ./path/to/assets

Confirm that the served files are injected with the correct source map comment in production in dev tools.

//# chunkId=0197e6db-9a73-7b91-9e80-4e1b7158db5c

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

# Upload assets to posthog
posthog-cli sourcemap upload --directory ./path/to/assets

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

Serve injected assets

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. We suggest you upload source maps right after your production build in CI.

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.