after crash nodered logs:
4 Sep 08:22:55 - [red] Uncaught Exception: 4 Sep 08:22:55 - ReferenceError: undefindenFunction is not defined at Function node:cdf5d431.98a838 [Camera Init]:14:5 nodered.service: Main process exited, code=exited, status=1/FAILURE
so you do know what crashed and you can tell this to the user:
function node: **[Camera Init]** caused a crash reason: ReferenceError: undefindenFunction is not defined at Function
nodered.service: Unit entered failed state.
failed state could present a web page that displays the above information and the complete log for more information
in the .node-red folder you have
you could present the user a button that restores the backup and present other ways to exit the
failed state or even teach him how to use try/catch
user experience could better as long as the user does not see the default page not found of the browser.
nodered is about simplicity and ease of use and leaving a newcomer that opened noederd for the first time disconnected form the server for a typo is not something that you want for new users.
If you are in production, you'd want the system to restart quickly instead of serve a webpage.
good point here, but pushing a kid or his teacher into the terminal is not a good experience either