PageSourceSearch

https://www.historytoday.com/modules/contrib/raven/js/raven.js?v=4.2.0

js historytoday.com collected 2026-10-01 09:16:19 UTC 1,751 bytes, 46 lines download raw bytes

1/**
2 * @file
3 * Configures @sentry/browser with the Sentry DSN and extra options.
4 */
5
6((drupalSettings, Sentry) => {
7  // Add the browser performance tracing integration.
8  drupalSettings.raven.options.integrations.push(
9    // Additional browser tracing options can be applied by modifying
10    // drupalSettings.raven.browserTracingOptions in custom PHP or JavaScript.
11    Sentry.browserTracingIntegration(
12      drupalSettings.raven.browserTracingOptions,
13    ),
14  );
15
16  // Show report dialog via beforeSend callback, if enabled.
17  if (drupalSettings.raven.showReportDialog) {
18    drupalSettings.raven.options.beforeSend = (event) => {
19      if (event.exception) {
20        Sentry.showReportDialog({ eventId: event.event_id });
21      }
22      return event;
23    };
24  }
25
26  // Set trace propagation targets, if configured.
27  if (drupalSettings.raven.tracePropagationTargets) {
28    drupalSettings.raven.options.tracePropagationTargets =
29      drupalSettings.raven.options.tracePropagationTargets || [];
30    // Automatically add same-origin relative URL pattern to the list.
31    drupalSettings.raven.options.tracePropagationTargets.push(/^\/(?!\/)/);
32    drupalSettings.raven.tracePropagationTargets.forEach((value) =>
33      drupalSettings.raven.options.tracePropagationTargets.push(
34        new RegExp(value, 'i'),
35      ),
36    );
37  }
38
39  // Additional Sentry configuration can be applied by modifying
40  // drupalSettings.raven.options in custom PHP or JavaScript. Use the latter
41  // for Sentry callback functions; library weight can be used to ensure your
42  // custom settings are added before this file executes.
43  Sentry.init(drupalSettings.raven.options);
44
45  Sentry.setUser({ id: drupalSettings.user.uid });
46})(window.drupalSettings, window.Sentry);

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.