upload-sourcemaps “bad reference to source” Error After Angular 19 Update

[andreialecu]

CLI Version

2.41.1

Operating System and Architecture

• macOS (arm64)
• macOS (x86_64)
• Linux (i686)
• Linux (x86_64)
• Linux (armv7)
• Linux (aarch64)
• Windows (i686)
• Windows (x86_64)

Operating System Version

macOS 14.6.1

Link to reproduction repository

No response

CLI Command

COMMIT_HASH=$(git rev-parse HEAD) sentry-cli releases -o <organization-name> -p <project-name> files $COMMIT_HASH upload-sourcemaps <build-directory>

Exact Reproduction Steps

After upgrading to Angular 19 and running our build scripts it appears that the step to upload-sourcemaps using the sentry-cli fails with just:

> Found 287 files
> Analyzing 287 sources
> Analyzing completed in 0.063s
> Rewriting sources
error: bad reference to source #8

I cannot see more details about this even if I enable logging, and I cannot share the repo as it's not public.

Expected Results

The Sentry CLI successfully uploads the source maps without any errors.

Actual Results

The Sentry CLI fails during the analysis and rewriting phase with the error:

error: bad reference to source #8

Logs

  DEBUG   2025-01-27 11:01:25.315104 +02:00 whitelisting builds/asdf/chunk-5AVHIDNV.js.map: Whitelist(IgnoreMatch(Types(Glob(Matched { def: FileTypeDef { name: "map", globs: ["*.map"] } }))))  (from ignore)
  INFO    2025-01-27 11:01:25.315137 +02:00 found: builds/asdf/chunk-5AVHIDNV.js.map (187487 bytes)
  DEBUG   2025-01-27 11:01:25.315247 +02:00 whitelisting builds/asdf/chunk-JULAKFHO.js: Whitelist(IgnoreMatch(Types(Glob(Matched { def: FileTypeDef { name: "js", globs: ["*.js"] } }))))  (from ignore)
  INFO    2025-01-27 11:01:25.315261 +02:00 found: builds/asdf/chunk-JULAKFHO.js (1179 bytes)
> Found 287 files
> Analyzing 287 sources
> Analyzing completed in 0.063s
> Rewriting sources
error: bad reference to source #8
  INFO    2025-01-27 11:01:25.793425 +02:00 Skipping update nagger update check

[andreialecu]

Adding --no-rewrite seems to make the command not error out.

Haven't yet verified if it actually makes the sourcemaps work properly in Sentry though.

[andreiborza]

Hi @andreialecu, thanks for filing this.

Another user reported this on discord, they mentioned tracing this issue back to esbuild's 0.24.1 release. We're still investigating, but for the meantime, if you're using esbuild, could you try downgrading it to 0.24.0?

[scomans]

Hi @andreialecu, thanks for filing this.

Another user reported this on discord, they mentioned tracing this issue back to esbuild's 0.24.1 release. We're still investigating, but for the meantime, if you're using esbuild, could you try downgrading it to 0.24.0?

If you are using PNPM you can pin the version of esbuild like this:

  "pnpm": {
    "overrides": {
      "@angular/build>[email protected]": "0.24.0"
    }
  }

[andreialecu]

Thank you for the fast turnaround. I'm using Yarn, and added a resolution to 0.24.0

I can confirm that it indeed works with esbuild 0.24.0

[andreiborza]

Thanks for taking the time to file this and for finding the workaround @scomans.

We'll have to do some digging on this one.

[loewenheim]

One problem here is definitely that there is no indication which sourcemap file was being processed when the error happened. cc @szokeasaurusrex

[szokeasaurusrex]

Indeed @loewenheim. I've been looking into how to improve our error messages for things like this, so hopefully we can improve behavior here, as well

[kle-pra]

Same problems on our angular 19 project, but suprisingly not all of them.

For npm, the workaround is:

"overrides": {
    "@angular/build": {
      "esbuild": "0.24.0"
    }