Skip to content

Improve microfrontend error handling

Mael Gaonach requested to merge 332-app-will-fail-to-start-without-logistics into main

Closes #332 (closed), #344 (closed)

Issue reported in #332 (closed) was due to the error message for failed to fetch dynamically imported module being different in firefox, so it was not properly detected as an remote import error and was not caught.

This MR addresses this problem detecting firefox's message as an remote import error too, and by catching any type of error comming from the microfronted, not just import error.

As microfrontends are designed to be optional, the rest of the app can continue working when one of them is broken.

When an error 'remote component could not be loaded' is detected: image

When any other type or error is detected: image

You can click on the icon to see stack trace (useless for user but useful for admins or if you happen to be with the user): image image

'Report this error' Opens email editor to feedback email including the stack trace and URL.

Edited by Mael Gaonach

Merge request reports