feat: runtime error logging

[kaljarv]

It'd be nice to also catch unexpected errors on CSR.

• https://khromov.se/building-a-privacy-friendly-self-hosted-application-architecture-with-sveltekit/

See also

• 532

[kaljarv]

• Check if we could combine GlitchTip with Umami or others in a container so we don't need to have gazillions of these
• Check if it's possible to just intercept client errors and use a Sveltekit API route to write these on disk

[norppaa]

Running things in the same container is possible though not necessarily a good practise as it might lead to conflicts or performance issues. Docker docs

Client errors can be intercepted using with for example the js functions window.onerror and window.onunhandlerejection or try-catch-finally blocks and afterwards sending them to the backend to be logged. Logging can be done manually or using libraries such as winston or pino. An API route also needs to be implemented to receive error details from the client.

Sending user information to the backend requires consent from the user.

Do we need error boundaries to contain errors in a single component so that the whole app does not crash? This is not implemented by svelte.

One discussion about error handling with hooks

[kaljarv]

Next, try this out in a simple model which only counts errors per route (and saves generic data, such as user agent).