feat(nuxt): Improve docs based on feedback

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).
@@ -483,14 +483,14 @@ Learn more about fixing these caching issues in the <PlatformLink to="/sourcemap
     ```json {tabTitle:pnpm} {filename:package.json}
     "pnpm": {
       "overrides": {
-      "@vercel/nft": "^0.27.4"
+        "@vercel/nft": "^0.27.4"
+      }
     }
-  }
     ```
 
   </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.
@@ -517,22 +517,22 @@ Learn more about fixing these caching issues in the <PlatformLink to="/sourcemap
 
     ```json {tabTitle:npm} {filename:package.json}
     "overrides": {
-      "nitropack": "2.9.7",
+      "nitropack": "~2.9.7",
       "@vercel/nft": "^0.27.4"
     }
     ```
 
     ```json {tabTitle:yarn} {filename:package.json}
     "resolutions": {
-      "nitropack": "2.9.7",
+      "nitropack": "~2.9.7",
       "@vercel/nft": "^0.27.4"
     }
     ```
 
     ```json {tabTitle:pnpm} {filename:package.json}
     "pnpm": {
       "overrides": {
-        "nitropack": "2.9.7",
+        "nitropack": "~2.9.7",
         "@vercel/nft": "^0.27.4"
       }
     }

docs/platforms/javascript/guides/nuxt/install/dynamic-import.mdx

@@ -33,20 +33,20 @@ We are working on figuring this out ([see issue here](https://github.com/getsent
 
 ```json {tabTitle:npm} {filename:package.json}
 "overrides": {
-  "nitropack": "2.9.7",
+  "nitropack": "~2.9.7",
   "@vercel/nft": "^0.27.4"
 }
 ```
 ```json {tabTitle:yarn} {filename:package.json}
 "resolutions": {
-  "nitropack": "2.9.7",
+  "nitropack": "~2.9.7",
   "@vercel/nft": "^0.27.4"
 }
 ```
 ```json {tabTitle:pnpm} {filename:package.json}
 "pnpm": {
   "overrides": {
-    "nitropack": "2.9.7",
+    "nitropack": "~2.9.7",
     "@vercel/nft": "^0.27.4"
   }
 }

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
@@ -161,16 +161,24 @@ 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:
+The Sentry Nuxt Module automatically enables source map generation for your project,
+but you'll need to enable it explicitly for the client-side. Add this 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 'hidden' option functions the same as `true`, by enabling source map generation, but it also suppresses the source map reference comments that would
+normally appear at the end of each generated file in the build output. This keeps the source maps available without exposing their references in the files.
+
+When you open browser developer tools, browsers try to fetch source maps using reference comments in bundled files. If source maps are uploaded to Sentry and
+removed from the client-side, these references cause 404 errors in developer tools. The `'hidden'` option stops these comments from being generated, preventing browsers
+from trying to fetch missing files and avoiding unnecessary errors.
+
+You need to explicitly enable client-side source maps because Nuxt applies default [source map settings](https://nuxt.com/docs/api/nuxt-config#sourcemap), and
+the Sentry Nuxt Module respects these when they are explicitly defined.
 
 ## Verify
 

platform-includes/getting-started-install/javascript.nuxt.mdx

@@ -1,7 +1,7 @@
 We recommend installing the SDK by running our installation wizard in the root directory of your project:
 
 ```bash
-npx @sentry/wizard@latest -i nuxt --org ___ORG_SLUG___ --project ___PROJECT_SLUG___
+npx @sentry/wizard@latest -i nuxt
 ```
 
 The wizard will prompt you to log in to Sentry. It will then automatically do the following steps for you: