> AI agents: this is one page from PostHog's docs. Full index of Markdown docs for LLMs: https://posthog.com/llms.txt # Upload source maps for React Canonical URL: https://posthog.com/docs/error-tracking/upload-source-maps/react ## On this page - [AI wizard](#ai-wizard) - [Manual setup](#manual-setup) - [Install the PostHog CLI](#install-the-posthog-cli) - [Authenticate the PostHog CLI](#authenticate-the-posthog-cli) - [Output source maps for your framework](#output-source-maps-for-your-framework) - [Inject source map](#inject-source-map) - [Verify source map injection](#verify-source-map-injection) - [Upload source map](#upload-source-map) - [Verify source maps upload](#verify-source-maps-upload) ## AI wizard Set up source map uploading automatically with our wizard by running this command in your project directory with your terminal (it also works for [LLM coding agents](https://posthog.com/blog/envoy-wizard-llm-agent.md) like Cursor and Bolt): `npx @posthog/wizard upload-source-maps` ## Manual setup 1. 1 ## Install the PostHog CLI Required Install `posthog-cli`: ### Npm ```bash npm install -g @posthog/cli ``` ### Curl ```bash curl -LsSf https://download.posthog.com/cli | sh ``` ### Homebrew ```bash brew install posthog/tap/posthog-cli ``` ### Cargo ```bash cargo install posthog-cli ``` 2. 2 ## Authenticate the PostHog CLI Required To authenticate the CLI, call the `login` command. This opens your browser where you select your organization, project, and API scopes to grant: ```bash 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: | Environment Variable | Description | Source | | --- | --- | --- | | `POSTHOG_CLI_HOST` | The PostHog host to connect to \[default: https://us.posthog.com\] | [Project settings](https://app.posthog.com/settings/project#variables) | | `POSTHOG_CLI_PROJECT_ID` | PostHog project ID | [Project settings](https://app.posthog.com/settings/project#variables) | | `POSTHOG_CLI_API_KEY` | **Personal API key** with `error tracking write` and `organization read` scopes | [API key settings](https://app.posthog.com/settings/user-api-keys#variables) | You can also use the `--host` option instead of the `POSTHOG_CLI_HOST` environment variable to target a different PostHog instance or region. For EU users: ```bash posthog-cli --host https://eu.posthog.com [CMD] ``` 3. 3 ## Output source maps for your framework Required If you're using React with Vite, you can enable source maps in your `vite.config.js` file. ```javascript import { defineConfig } from 'vite' import react from '@vitejs/plugin-react' export default defineConfig({ plugins: [react()], build: { sourcemap: true, } }) ``` If you're using another build tool like [webpack](https://webpack.js.org/configuration/devtool/) or [Rollup](https://rollupjs.org/configuration-options/#output-sourcemap), consult the documentation for your build tool to enable source maps. 4. 4 ## Inject source map Required Once you've built your application and have bundled assets, inject the context required by PostHog to associate the maps with the served code. ```bash # Inject release and chunk metadata into sourcemaps posthog-cli sourcemap inject --directory ./path/to/assets ``` 5. ## Verify source map injection Checkpoint *Confirm source map comments are present* Confirm that the served files are injected with the correct source map comment in production in dev tools. ```javascript //# chunkId=0197e6db-9a73-7b91-9e80-4e1b7158db5c ``` 6. 5 ## Upload source map Required You will then need to upload the modified assets to PostHog. ```bash # Upload injected sourcemaps to their release posthog-cli sourcemap upload --directory ./path/to/assets --release-name my-app --release-version 1.2.3 --build 42 ``` The CLI will create or reuse the [release](https://posthog.com/docs/error-tracking/releases.md) for the detected or supplied release name and version. The CLI will try to detect release name and version information, but you can set them explicitly with `--release-name` and `--release-version`. We recommend setting the release name, 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 also pass `--build` to record a build number (e.g. `CFBundleVersion` on iOS, `versionCode` on Android) as release metadata. This is optional — when omitted, no build info is recorded. > **💡 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. 8. ## Verify source maps upload Checkpoint Confirm that source maps are successfully uploaded to PostHog.[Check symbol sets in PostHog](https://app.posthog.com/error_tracking/configuration#selectedSetting=error-tracking-symbol-sets)