Tim Fish
Tim Fish
Ah yes sorry you are correct, I didn't realise `setupIntegrations` was overridden in the client. I guess this code need to be copied from Sentry core: https://github.com/getsentry/sentry-javascript/blob/7303cdacb3ba2da1e71844e9daa5ffdb91d9a8a7/packages/core/src/integration.ts#L106-L130
My [initial run of e2e tests](https://github.com/getsentry/sentry-electron/actions/runs/3874232367) for `@sentry/electron` showed this failing for v13 to v22. It may well go back further but these are the only versions we test that...
I've been working on this: https://github.com/timfish/sentry-deno
Noisy, as in just too many json spans? We could make an integration with a configurable threshold and then only enable it be default for Node? Or enabled by default...
As far as I can tell, the reproduction repository supplied by @xr0master doesn't reproduce a memory leak. I've load tested the endpoint and regardless of whether I use v7.84.0, v7.91.0...
> this works great with the Sentry Node plugin > I still see the problem in the latest version of the React and Electron plugins Do you mean that in...
With the latest SDK and the following code: `index.js` ```ts const path = require("path"); const { inspect } = require("util"); const { app, BrowserWindow } = require("electron"); const { init...
The Electron SDKs default transport handles offline queueing but also has some callbacks which can be used to create a more effective opt-in mechanism since events can be queued to...
> great package name Oh, it's completely stolen from the [Rust crate](https://crates.io/crates/sadness-generator) that it wraps. I think we can thank @Jake-Shadle for this 🤣