If there was an error in the callback provided by the user in the addEventListener plugin method, the application did not handle this error properly - error failed silently, i.e. there was no information in the console and it blocked rest event callbacks from being called.
Piotr asked to display an error in the console with the correct stacktrace, so I also solved the MIN-294 task here, because the stacktrace without the added "//# sourceURL=URL" showed the incorrect stacktrace and logging error didn't make sense.
Piotr mentioned that it would be ideal if we displayed a box for the user with the information: "plugin "plugin name" crashed and he should contact plugin developer", so I added a toast with this information.
Additionally, an issue with failed tests in the development branch has been resolved
The video demonstrates the correct stack trace, including the accurate plugin script names, and illustrates that after encountering an error, it still proceeds to call the remaining callbacks.