From 2fbaa0b9a1a24a0f23118bbdff30eca47a23b14e Mon Sep 17 00:00:00 2001
From: Charly Gomez <charly.gomez@sentry.io>
Date: Fri, 6 Dec 2024 10:13:47 +0100
Subject: [PATCH] add permalink flag

---
 docs/platforms/javascript/common/troubleshooting/index.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/platforms/javascript/common/troubleshooting/index.mdx b/docs/platforms/javascript/common/troubleshooting/index.mdx
index 30d0f6a0d4927..9d416643be8d7 100644
--- a/docs/platforms/javascript/common/troubleshooting/index.mdx
+++ b/docs/platforms/javascript/common/troubleshooting/index.mdx
@@ -459,7 +459,7 @@ Learn more about fixing these caching issues in the <PlatformLink to="/sourcemap
 </PlatformSection>
 
 <PlatformSection supported={['javascript.nuxt']}>
-  <Expandable title="Failed to register 'import-in-the-middle' during build time">
+  <Expandable permalink title="Failed to register 'import-in-the-middle' during build time">
     After adding `sentry.server.config.ts` and building the project, you might get an error like this:
     `Failed to register ESM hook import-in-the-middle/hook.mjs`. You can add an override (npm/pnpm) or a resolution (yarn)
     for `@vercel/nft` to fix this. This will add the `hook.mjs` file to your build output. See the [underlying issue in the UnJS Nitro project](https://github.com/unjs/nitro/issues/2703).
@@ -490,7 +490,7 @@ Learn more about fixing these caching issues in the <PlatformLink to="/sourcemap
 
   </Expandable>
 
-  <Expandable title="pnpm dev: Cannot find package 'import-in-the-middle'">
+  <Expandable permalink title="pnpm dev: Cannot find package 'import-in-the-middle'">
 
     Sentry injects `import "import-in-the-middle/hook.mjs"` in your server entry. This import acts as a hint for node bundlers to really include this file.
     As pnpm implements a strict dependency isolation, this import might cause problems.