move source maps options away from Next.js manual setup page (#12783)

* move manual setup source maps options from Next.js manual setup page 
* remove duplicate link from next.js source maps page

Author: inventarSarah

docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx

@@ -150,6 +150,16 @@ If set to `true`, the Sentry SDK will attempt to tree-shake code related to trac
 
 Include Next.js-internal code and code from dependencies when uploading source maps.
 
+<Expandable type="note" title="When and why to widen the upload scope.">
+  If you find that there are some frames in your client-side stack traces that
+  aren't getting source-mapped even when most others are, the issue might be
+  that those frames are from files in `static/chunks/` rather than
+  `static/chunks/pages/`. By default, such files aren't uploaded because the
+  majority of the files in `static/chunks/` only contain Next.js or third-party
+  code. To upload all of the files and source maps, including ones from
+  third-party packages, set the `widenClientFileUpload` option to `true`.
+</Expandable>
+
 Note: Enabling this option can lead to longer build times.
 
 </SdkOption>

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

@@ -67,13 +67,14 @@ export default withSentryConfig(nextConfig, {
 ```
 
 ### Extend Sentry Webpack Plugin Options
+
 `withSentryConfig` uses a [custom Webpack plugin](https://www.npmjs.com/package/@sentry/webpack-plugin) to manage your sourcemaps and releases under the hood. If `withSentryConfig` does not provide the option you need to modify, you may override the `sentryWebpackPluginOptions` directly via `unstable_sentryWebpackPluginOptions`.
 
 <Alert level="warning">
-  Note that this option is unstable and its API may include breaking changes in any release.
+  Note that this option is unstable and its API may include breaking changes in
+  any release.
 </Alert>
 
-
 ## Create Initialization Config Files
 
 Create three files in the root directory of your Next.js application: `sentry.client.config.js`, `sentry.server.config.js` and `sentry.edge.config.js`. In these files, add your initialization code for the client-side SDK and server-side SDK, respectively. We've included some examples below.
@@ -175,7 +176,6 @@ export async function register() {
 }
 ```
 
-
 Make sure that the `import` statements point to your newly created `sentry.server.config.(js|ts)` and `sentry.edge.config.(js|ts)` files.
 
 ## Report React Component Render Errors
@@ -457,60 +457,6 @@ Do not commit your auth token to version control.
 SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___
 ```
 
-### Disable Source Maps
-
-You can disable the custom sourcemap plugin as follows:
-
-```javascript {tabTitle:ESM} {filename:next.config.mjs}
-export default withSentryConfig(nextConfig, {
-  sourcemaps: {
-    disable: true,
-  },
-});
-```
-
-```javascript {tabTitle:CJS} {filename:next.config.js}
-module.exports = withSentryConfig(nextConfig, {
-  sourcemaps: {
-    disable: true,
-  },
-});
-```
-
-### Use `hidden-source-map`
-
-Depending on your deployment setup, adding `sentry/nextjs` to your app may cause your source code to be visible in browser devtools when it wasn't before. (This happens because of the default behavior of [webpack's `source-map` built-in `devtool`](https://webpack.js.org/configuration/devtool/).) To prevent this, you can use `hidden-source-map` rather than `source-map`, which will prevent your built files from containing a `sourceMappingURL` comment, thus making sourcemaps invisible to the browser. To use `hidden-source-map`, add a `sentry` object to `nextConfig` above, and set the `hideSourceMaps` option to `true`:
-
-```javascript {tabTitle:ESM} {filename:next.config.mjs}
-export default withSentryConfig(nextConfig, {
-  hideSourceMaps: true,
-});
-```
-
-```javascript {tabTitle:CJS} {filename:next.config.js}
-module.exports = withSentryConfig(nextConfig, {
-  hideSourceMaps: true,
-});
-```
-
-### Widen the Upload Scope
-
-If you find that there are some frames in your client-side stack traces that aren't getting source-mapped even when most others are, the issue might be that those frames are from files in `static/chunks/` rather than `static/chunks/pages/`. By default, such files aren't uploaded because the majority of the files in `static/chunks/` only contain Next.js or third-party code.
-
-To upload all of the files and source maps, including ones from third-party packages, set the `widenClientFileUpload` option to `true`:
-
-```javascript {tabTitle:ESM} {filename:next.config.mjs}
-export default withSentryConfig(nextConfig, {
-  widenClientFileUpload: true,
-});
-```
-
-```javascript {tabTitle:CJS} {filename:next.config.js}
-module.exports = withSentryConfig(nextConfig, {
-  widenClientFileUpload: true,
-});
-```
-
 ## Configure Tunneling to avoid Ad-Blockers
 
 You might notice that Sentry events are sometimes blocked by ad blockers.

platform-includes/sourcemaps/primer/javascript.nextjs.mdx

@@ -1,3 +1,3 @@
 `@sentry/nextjs` will generate and upload source maps automatically, in order to enable errors to have readable stack traces.
 
-To upload source maps, the `@sentry/nextjs` SDK uses the [Sentry webpack plugin](https://www.npmjs.com/package/@sentry/webpack-plugin) under the hood. See the [Manual Configuration](../manual-setup/#configure-source-maps) page and the Sentry [webpack plugin documentation](https://www.npmjs.com/package/@sentry/webpack-plugin) for more details. If you are using Vercel, then you can also use the [Vercel integration](/organization/integrations/deployment/vercel/) to upload source maps during deployments automatically.
+To upload source maps, the `@sentry/nextjs` SDK uses the Sentry webpack plugin under the hood. See the [Build Options](../configuration/build/#source-maps-options) page and the Sentry [webpack plugin documentation](https://www.npmjs.com/package/@sentry/webpack-plugin) for more details. If you are using Vercel, then you can also use the [Vercel integration](/organization/integrations/deployment/vercel/) to upload source maps during deployments automatically.