From d335b741fe8eced583e4e52f652da637d92bb5fb Mon Sep 17 00:00:00 2001
From: Luca Forstner <luca.forstner@sentry.io>
Date: Wed, 20 Nov 2024 16:12:05 +0100
Subject: [PATCH] Use `@sentry/core` instead of `@sentry/utils`

---
 .../distributed-tracing/custom-instrumentation/javascript.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx b/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
index a27adc4b2cd0a..22ba2d3cf36b7 100644
--- a/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
+++ b/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
@@ -83,7 +83,7 @@ Some Sentry backend SDKs provide a built-in way to inject these `<meta>` tags in
 Then, on `pageload` you can do the following:
 
 ```javascript
-import { propagationContextFromHeaders } from "@sentry/utils";
+import { propagationContextFromHeaders } from "@sentry/core"; // Before version 8.40.0, import from "@sentry/utils"
 import * as Sentry from "@sentry/browser";
 
 // Read meta tag values