feat(nuxt): Improve docs based on feedback

Author: s1gr1d

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="'import-in-the-middle' error during startup">
+  <Expandable 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 permalink title="pnpm: Resolving 'import-in-the-middle' external package errors">
+  <Expandable 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.

docs/platforms/javascript/guides/nuxt/manual-setup.mdx

@@ -82,8 +82,8 @@ Add a `sentry.client.config.ts` file to the root of your project (this is probab
 import * as Sentry from '@sentry/nuxt';
 
 Sentry.init({
-  // If set up, you can use your runtime config here
-  // dsn: useRuntimeConfig().public.sentry.dsn,
+  // If set up, you can use the Nuxt runtime config here
+  // dsn: useRuntimeConfig().public.sentry.dsn, // modify, depending on your custom runtime config
   dsn: "___PUBLIC_DSN___",
 
   // We recommend adjusting this value in production, or using tracesSampler
@@ -162,15 +162,18 @@ export default defineNuxtConfig({
 ```
 
 To upload source maps, the Sentry Nuxt Module will automatically enable source map generation in your project if it is not already enabled.
-However, you need to explicitly enable source map generation on the client-side. To do this, add the following code to your Nuxt configuration:
+However, you need to explicitly enable source map generation on the client-side.
+To do this, add the following code to your Nuxt configuration:
 
 ```javascript {filename:nuxt.config.ts} {2}
 export default defineNuxtConfig({
-    sourcemap: { client: true }
+    sourcemap: { client: 'hidden' }
 });
 ```
 
-This step is necessary because Nuxt sets default values for source maps ([Nuxt docs](https://nuxt.com/docs/api/nuxt-config#sourcemap)), and the Sentry Nuxt Module keeps these settings when they are explicitly defined.
+The option `'hidden'` works like `true`, but suppresses the source map reference comments that would be added to the end of each generated file in the build output.
+
+Explicitly enabling client source maps is necessary because Nuxt sets default values for source maps ([Nuxt docs](https://nuxt.com/docs/api/nuxt-config#sourcemap)), and the Sentry Nuxt Module keeps these settings when they are explicitly defined.
 
 ## Verify