Usage with the Qwik framework

[Kocal]

Hi everyone, I would like to know what are the best practices to use Sentry with Qwik, a relatively new web framework with a new approach to performance optimization (resumability).

Qwik runs on two sides, server and browser: https://qwik.builder.io/docs/guides/qwik-nutshell/#run-code-only-in-the-browser

I didn't try yet but I hope there is no issue if we manually call Sentry.captureException() for exception we throw ourselves (e.g.: fetching an external API failed), but errors thrown by Qwik itself?

I know QwikDev/qwik#2618 already exists, but I think this is nice to open the conversation here.

Thanks! 🙏🏻

/cc @jessezhang91 @mhevery @zanettin

[jessezhang91]

The way we have it set up on our end, we have one Sentry project for the UI and one for the server (different DSNs).

For the UI, we have the standard browser code in a useVisibleTask$.

For the server (we use express), we have the standard express server code in the entry.express.tsx that Qwik auto-generated.

[AbhiPrasad]

Yup you'll have to use two different SDKs - @sentry/browser for the frontend, and @sentry/node for the server.

[Kocal]

Thanks for the confirmation! :)

[AbhiPrasad]

As long as quik themselves does not swallow the error (which it seems like it does from looking at QwikDev/qwik#2618), the respective browser/node sdks should capture the unhandled exceptions that bubble up to global error listeners.

re: https://github.com/BuilderIO/qwik/blob/70880b71995361202ae0b4725454cb2bd008ab2d/packages/qwik/src/core/util/log.ts#L10-L16

The best way to get around the limitation of the error not being exposed it to monkeypatch the method, this is easy to do with an npm git patch https://www.npmjs.com/package/patch-package

[mhevery]

Fixed in QwikDev/qwik#5029

[AbhiPrasad]

Thanks for the quick turnaround @mhevery!