@getsupertab/supertab-js 3.4.3 → 3.6.0

package/dist/pkg/prod/sentry-D9KGWpW4.js

@@ -1,42 +0,0 @@
-import * as a from "@sentry/react";
-import { T as l, P as m, a as c, V as E } from "./sdk-BkB1ahBa.js";
-a.init({
-  dsn: E,
-  release: `${m}@${c}`,
-  environment: l,
-  integrations: [
-    a.browserTracingIntegration(),
-    a.replayIntegration()
-  ],
-  beforeSend: (e) => {
-    var r, t;
-    return ((t = (r = e.exception) == null ? void 0 : r.values) == null ? void 0 : t.some(
-      (i) => {
-        var n, s;
-        return (s = (n = i.stacktrace) == null ? void 0 : n.frames) == null ? void 0 : s.some(
-          (p) => {
-            var o;
-            return (o = p.filename) == null ? void 0 : o.match(/tab\.js|bundle\.js/);
-          }
-        );
-      }
-    )) ? e : null;
-  },
-  tracesSampleRate: 1,
-  //  Capture 100% of the transactions
-  // Set profilesSampleRate to 1.0 to profile every transaction.
-  // Since profilesSampleRate is relative to tracesSampleRate,
-  // the final profiling rate can be computed as tracesSampleRate * profilesSampleRate
-  // For example, a tracesSampleRate of 0.5 and profilesSampleRate of 0.5 would
-  // results in 25% of transactions being profiled (0.5*0.5=0.25)
-  profilesSampleRate: 1,
-  // Session Replay
-  replaysSessionSampleRate: 0.1,
-  // This sets the sample rate at 10%. You may want to change it to 100% while in development and then sample at a lower rate in production.
-  replaysOnErrorSampleRate: 1
-  // If you're not already sampling the entire session, change the sample rate to 100% when sampling sessions where errors occur.
-});
-const u = (e) => a.captureException(e);
-export {
-  u as captureException
-};