Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

minor: support @sentry/sveltekit routing instrumentation #98

Merged
6 commits merged into from
Oct 22, 2023
Merged
Show file tree
Hide file tree
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -46,19 +46,20 @@
},
"devDependencies": {
"@playwright/test": "1.39.0",
"@sentry/types": "^7.74.1",
"@typescript-eslint/eslint-plugin": "6.8.0",
"@typescript-eslint/parser": "6.8.0",
"eslint-config-prettier": "9.0.0",
"eslint-plugin-svelte": "2.34.0",
"prettier-plugin-svelte": "3.0.3",
"typescript": "5.2.2"
},
"dependencies": {
"typescript": "5.2.2",
"@sentry/core": "7.74.1",
"@sentry/svelte": "7.74.1",
"@sentry/utils": "7.74.1",
"@sveltejs/kit": "1.26.0",
"esm-env": "1.0.0",
"toucan-js": "3.3.0"
},
"dependencies": {
"esm-env": "1.0.0"
}
}
2 changes: 1 addition & 1 deletion packages/lib/scripts/build.ts
Original file line number Diff line number Diff line change
Expand Up @@ -6,5 +6,5 @@ build({
outfile: '../../dist/index.js',
minify: true,
format: 'esm',
external: ['esm-env']
external: ['esm-env', '$app/stores']
})
24 changes: 24 additions & 0 deletions packages/lib/src/client/addClientIntegrations.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
import { hasTracingEnabled } from '@sentry/core'
import { BrowserOptions, BrowserTracing } from '@sentry/svelte'
import { addOrUpdateIntegration } from '@sentry/utils'
import { svelteKitRoutingInstrumentation } from './router.js'

export const addClientIntegrations = (options: BrowserOptions) => {
let integrations = options.integrations || []

if (hasTracingEnabled(options)) {
const defaultBrowserTracingIntegration = new BrowserTracing({
routingInstrumentation: svelteKitRoutingInstrumentation
})

integrations = addOrUpdateIntegration(
defaultBrowserTracingIntegration,
integrations,
{
'options.routingInstrumentation': svelteKitRoutingInstrumentation
}
)
}

options.integrations = integrations
}
Comment on lines +1 to +24
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The function addClientIntegrations modifies the options object passed to it. This can lead to unexpected side effects if the caller is not aware of this behavior. Consider returning a new object with the updated integrations instead of modifying the input object. This would make the function pure and easier to reason about.

-   options.integrations = integrations
+   return { ...options, integrations };

Then, the caller can decide whether to replace the original options object or not.

16 changes: 16 additions & 0 deletions packages/lib/src/client/applySdkMetadata.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
import { SDK_VERSION } from '@sentry/core'
import { BrowserOptions } from '@sentry/svelte'

const PACKAGE_NAME_PREFIX = 'npm:@sentry/'

export const applySdkMetadata = (options: BrowserOptions, names: string[]) => {
options._metadata = options._metadata || {}
options._metadata.sdk = options._metadata.sdk || {
name: 'sentry.javascript.sveltekit',
packages: names.map((name) => ({
name: `${PACKAGE_NAME_PREFIX}${name}`,
version: SDK_VERSION
})),
version: SDK_VERSION
}
}
Comment on lines +1 to +16
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The function applySdkMetadata modifies the options object passed to it. This is a side effect that could lead to unexpected behavior if the caller is not aware of it. Consider returning a new object instead of modifying the existing one. This would make the function pure and easier to reason about.

- export const applySdkMetadata = (options: BrowserOptions, names: string[]) => {
-   options._metadata = options._metadata || {}
-   options._metadata.sdk = options._metadata.sdk || {
-     name: 'sentry.javascript.sveltekit',
-     packages: names.map((name) => ({
-       name: `${PACKAGE_NAME_PREFIX}${name}`,
-       version: SDK_VERSION
-     })),
-     version: SDK_VERSION
-   }
- }
+ export const applySdkMetadata = (options: BrowserOptions, names: string[]): BrowserOptions => {
+   const newOptions = { ...options };
+   newOptions._metadata = newOptions._metadata || {}
+   newOptions._metadata.sdk = newOptions._metadata.sdk || {
+     name: 'sentry.javascript.sveltekit',
+     packages: names.map((name) => ({
+       name: `${PACKAGE_NAME_PREFIX}${name}`,
+       version: SDK_VERSION
+     })),
+     version: SDK_VERSION
+   }
+   return newOptions;
+ }

5 changes: 3 additions & 2 deletions packages/lib/src/client/init.ts
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@ import { addExceptionMechanism } from '@sentry/utils'
import type { HandleClientError } from '@sveltejs/kit'
import { DEV } from 'esm-env'
import { defaultErrorHandler } from './defaultErrorHandler'
import { sentryInit } from './sentryInit'

export const init = (
dsn: string,
Expand All @@ -18,12 +19,12 @@ export const init = (
return (handleError = defaultErrorHandler) => handleError
}

Sentry.init({
sentryInit({
dsn,
tracesSampleRate: 1.0,
replaysSessionSampleRate: 0.1,
replaysOnErrorSampleRate: 1.0,
integrations: [new Sentry.BrowserTracing(), new Sentry.Replay()],
integrations: [new Sentry.Replay()],
...sentryOptions
})

Expand Down
11 changes: 11 additions & 0 deletions packages/lib/src/client/restoreFetch.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
import { WINDOW } from '@sentry/svelte'

export const restoreFetch = (actualFetch: typeof fetch) => {
const globalWithSentryFetchProxy = WINDOW

// @ts-expect-error TODO: fix this
globalWithSentryFetchProxy._sentryFetchProxy =
globalWithSentryFetchProxy.fetch

globalWithSentryFetchProxy.fetch = actualFetch
}
123 changes: 123 additions & 0 deletions packages/lib/src/client/router.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,123 @@
import { navigating, page } from '$app/stores'
import { getActiveTransaction } from '@sentry/core'
import { WINDOW } from '@sentry/svelte'
import type { Transaction, TransactionContext } from '@sentry/types'
import type { Span } from '@sentry/types'

const DEFAULT_TAGS = {
'routing.instrumentation': '@sentry/sveltekit'
}

export const svelteKitRoutingInstrumentation = <T extends Transaction>(
startTransactionFn: (context: TransactionContext) => T | undefined,
startTransactionOnPageLoad?: boolean,
startTransactionOnLocationChange?: boolean
) => {
if (startTransactionOnPageLoad) {
instrumentPageload(startTransactionFn)
}

if (startTransactionOnLocationChange) {
instrumentNavigations(startTransactionFn)
}
}

const instrumentPageload = <T extends Transaction>(
startTransactionFn: (context: TransactionContext) => T | undefined
) => {
const initialPath = WINDOW && WINDOW.location && WINDOW.location.pathname

const pageloadTransaction = startTransactionFn({
name: initialPath,
op: 'pageload',
origin: 'auto.pageload.sveltekit',
description: initialPath,
tags: {
...DEFAULT_TAGS
},
metadata: {
source: 'url'
}
})

page.subscribe((page) => {
if (!page) {
return
}

const routeId = page.route && page.route.id

if (pageloadTransaction && routeId) {
pageloadTransaction.setName(routeId, 'route')
}
})
}

/**
* Use the `navigating` store to start a transaction on navigations.
*/
const instrumentNavigations = <T extends Transaction>(
startTransactionFn: (context: TransactionContext) => T | undefined
) => {
let routingSpan: Span | undefined = undefined
let activeTransaction

navigating.subscribe((navigation) => {
if (!navigation) {
// `navigating` emits a 'null' value when the navigation is completed.
// So in this case, we can finish the routing span. If the transaction was an IdleTransaction,
// it will finish automatically and if it was user-created users also need to finish it.
if (routingSpan) {
routingSpan.finish()
routingSpan = undefined
}
return
}

const from = navigation.from
const to = navigation.to

// for the origin we can fall back to window.location.pathname because in this emission, it still is set to the origin path
const rawRouteOrigin =
(from && from.url.pathname) ||
(WINDOW && WINDOW.location && WINDOW.location.pathname)

const rawRouteDestination = to && to.url.pathname

// We don't want to create transactions for navigations of same origin and destination.
// We need to look at the raw URL here because parameterized routes can still differ in their raw parameters.
if (rawRouteOrigin === rawRouteDestination) {
return
}

const parameterizedRouteOrigin = from && from.route.id
const parameterizedRouteDestination = to && to.route.id

activeTransaction = getActiveTransaction()

if (!activeTransaction) {
activeTransaction = startTransactionFn({
name: parameterizedRouteDestination || rawRouteDestination || 'unknown',
op: 'navigation',
origin: 'auto.navigation.sveltekit',
metadata: { source: parameterizedRouteDestination ? 'route' : 'url' },
tags: {
...DEFAULT_TAGS
}
})
}

if (activeTransaction) {
if (routingSpan) {
// If a routing span is still open from a previous navigation, we finish it.
routingSpan.finish()
}
routingSpan = activeTransaction.startChild({
op: 'ui.sveltekit.routing',
description: 'SvelteKit Route Change',
origin: 'auto.ui.sveltekit'
})
activeTransaction.setTag('from', parameterizedRouteOrigin)
}
})
}
26 changes: 26 additions & 0 deletions packages/lib/src/client/sentryInit.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
import { BrowserOptions, configureScope, init } from '@sentry/svelte'
import { addClientIntegrations } from './addClientIntegrations.js'
import { applySdkMetadata } from './applySdkMetadata.js'
import { restoreFetch } from './restoreFetch.js'
import { switchToFetchProxy } from './switchToFetchProxy.js'

export const sentryInit = (options: BrowserOptions) => {
applySdkMetadata(options, ['sveltekit', 'svelte'])

addClientIntegrations(options)

// 1. Switch window.fetch to our fetch proxy we injected earlier
const actualFetch = switchToFetchProxy()

// 2. Initialize the SDK which will instrument our proxy
init(options)

// 3. Restore the original fetch now that our proxy is instrumented
if (actualFetch) {
restoreFetch(actualFetch)
}

configureScope((scope) => {
scope.setTag('runtime', 'browser')
})
}
Comment on lines +1 to +26
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The sentryInit function is well-structured and follows a clear sequence of steps for initializing Sentry with SvelteKit. However, there is a potential issue with the restoreFetch function. If switchToFetchProxy fails and returns null or undefined, restoreFetch will be called with an undefined argument. This could lead to unexpected behavior or errors. Consider adding error handling or a check to ensure actualFetch is a function before restoring it.

  // 3. Restore the original fetch now that our proxy is instrumented
  if (actualFetch && typeof actualFetch === 'function') {
    restoreFetch(actualFetch)
  }

17 changes: 17 additions & 0 deletions packages/lib/src/client/switchToFetchProxy.ts
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
import { WINDOW } from '@sentry/svelte'

export function switchToFetchProxy() {
const globalWithSentryFetchProxy = WINDOW

const actualFetch = globalWithSentryFetchProxy.fetch

// @ts-expect-error TODO: fix this
if (globalWithSentryFetchProxy._sentryFetchProxy && actualFetch) {
globalWithSentryFetchProxy.fetch =
// @ts-expect-error TODO: fix this
globalWithSentryFetchProxy._sentryFetchProxy
return actualFetch
}

return undefined
}
Comment on lines +1 to +17
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The function switchToFetchProxy switches the global fetch function to a Sentry proxy. However, it doesn't check if the _sentryFetchProxy is a function before assigning it to fetch. This could potentially break the application if _sentryFetchProxy is not a function. Consider adding a type check before the assignment.

- if (globalWithSentryFetchProxy._sentryFetchProxy && actualFetch) {
+ if (typeof globalWithSentryFetchProxy._sentryFetchProxy === 'function' && actualFetch) {

Also, the function returns undefined if the conditions are not met. This could lead to unexpected behavior in the calling code. Consider throwing an error or returning a default value instead.

Loading