Add Resources and APM support

Author: BeltranBulbarellaDD

packages/core/src/tools/globalObject.ts

@@ -10,6 +10,11 @@ type XOR<T, U> = T | U extends object ? (Without<T, U> & U) | (Without<U, T> & T
 export type GlobalObject = XOR<Window, WorkerGlobalScope>
 
 export function getGlobalObject<T = typeof globalThis>(): T {
+  // Salesforce recommends to asign self to global: https://developer.salesforce.com/docs/platform/lightning-components-security/guide/lws-js.html#third-party-library-sets-up-on-global-window-object
+  if (typeof self === 'object') {
+    return self as unknown as T
+  }
+
   return globalThis as unknown as T
 }
 
@@ -21,3 +26,13 @@ export function getGlobalObject<T = typeof globalThis>(): T {
 export const globalObject = getGlobalObject<GlobalObject>()
 
 export const isWorkerEnvironment = 'WorkerGlobalScope' in globalObject
+
+export function getGlobalLocation<T extends { href: string } = Location>(): T | undefined {
+  return (globalObject as unknown as { location?: T }).location
+}
+
+// In Salesforce the location property must be used with accessors: https://developer.salesforce.com/docs/platform/lightning-components-security/guide/lws-limitations.html#:~:text=The%20location%20property%20must%20be%20used%20with%20these%20accessors.
+// If not we crash. This way we mantain current behaviour while fallbacking safely in Salesforce. 
+export function getGlobalLocationHref(): string {
+  return getGlobalLocation()!.href
+}

packages/core/src/tools/utils/urlPolyfill.ts

@@ -1,7 +1,7 @@
-import { globalObject } from '../globalObject'
+import { getGlobalLocationHref, globalObject } from '../globalObject'
 
 export function normalizeUrl(url: string) {
-  return buildUrl(url, location.href).href
+  return buildUrl(url, getGlobalLocationHref()).href
 }
 
 export function isValidUrl(url: string) {

packages/rum-core/src/domain/contexts/urlContexts.ts

@@ -5,8 +5,8 @@ import {
   createValueHistory,
   HookNames,
   DISCARDED,
-  mockable,
   buildUrl,
+  getGlobalLocationHref,
 } from '@datadog/browser-core'
 import type { LocationChange } from '../../browser/locationChangeObservable'
 import type { LifeCycle } from '../lifeCycle'
@@ -41,7 +41,7 @@ export function startUrlContexts(
   let previousViewUrl: string | undefined
 
   lifeCycle.subscribe(LifeCycleEventType.BEFORE_VIEW_CREATED, ({ startClocks, url }) => {
-    const locationHref = getLocationHref()
+    const locationHref = getGlobalLocationHref()
     const viewUrl = url !== undefined ? buildUrl(url, locationHref).href : locationHref
 
     urlContextHistory.add(
@@ -104,12 +104,3 @@ export function startUrlContexts(
     },
   }
 }
-
-// Preserves existing global location behavior but in Salesforce access through explicit window as documented:  https://developer.salesforce.com/docs/platform/lightning-components-security/guide/lws-limitations.html#:~:text=The%20location%20property,window.location
-function getLocationHref() {
-  try {
-    return mockable(location).href
-  } catch {
-    return mockable(window.location).href
-  }
-}