Source maps

Upload a release's source maps and a minified stack reads as the code you wrote, which is also how Rezee finds the commit likely behind an error.

Upload with the Rezee CLI

After each build, send the .map files for the release your SDK reports:

$ rezee sourcemaps upload dist --source 1042 --release web@1.4.2

--source is the number at the end of the source's DSN.
--release has to match the release the SDK sends, or the maps are never matched to a stack.
Each map is named by the prefix, ~/ by default, and its path under the directory, so uploading dist with files in dist/assets needs no prefix. Use --url-prefix ~/assets only when you upload the assets folder itself.
-w names the workspace when the clone does not.

Uploading needs a token that can write to Signals. See the CLI for signing in.

Or with sentry-cli

A build that already runs sentry-cli sourcemaps upload can keep it, pointed at Rezee - see Switching from Sentry.

Checked with sentry-cli 2.52. Only .map files are stored, each up to 20 MB.

The commit behind an error

Set a repository on the source in Settings → Signals. With the stack mapped back to your files, Rezee takes the deploy that went out just before the error first appeared, and shows the commits in it that touched the files at the top of the stack. A source with no repository, or a repository with no deploys, has no suspect; Rezee does not guess one from time alone.