This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

Indeed this is still happening, and since the original "AggregatedError" is encapsulated in an AxiosError you'll need to handle it as duck-typed:

try {
  // ...
catch (e) {
  let errMsg = e.errors ? e.errors.map((err) => err.toString()).join(', ') : e.toString();
  // ...
}

This is also happening for raw AggregateErrors as well, that at least should work.

PR very much welcome!

IDK what is going on but I am hitting the same roadblocker and IDK for how long we are gonna have this issue 😞

We're seeing a nondescript AggregateError running our Jest tests in a GHA workflow (https://github.com/sillsdev/TheCombine/actions/runs/10601707954/job/29382087602#step:7:47):

FAIL src/components/WordCard/tests/index.test.tsx
  ● WordCard › has summary and full views

    thrown: "Error: AggregateError

      at Object.dispatchError (node_modules/jsdom/lib/jsdom/living/xhr/xhr-utils.js:63:19)
      at Request.<anonymous> (node_modules/jsdom/lib/jsdom/living/xhr/XMLHttpRequest-impl.js:655:18)
      at ClientRequest.<anonymous> (node_modules/jsdom/lib/jsdom/living/helpers/http-request.js:121:14)
      at processTicksAndRejections (node:internal/process/task_queues:82:21)"
          at Array.map (<anonymous>)

@imnasnainaec hey! did you figure out the AggregateError issue? I am running into the exact same thing, and am completely clueless.