Show only next.js tree shaking section in next.js troubleshooting guide

Author: lforst

src/platforms/javascript/common/troubleshooting/index.mdx

@@ -408,7 +408,11 @@ Remember to pass in `true` as the second parameter to `addEventListener()`. With
 
 Sentry ships with code that enables you to <PlatformLink to="/configuration/options/#debug">debug your Sentry configuration</PlatformLink>. While this code can be very useful in development environments, it's not typically necessary to include it in your production bundles where it takes up valuable space. The JavaScript SDK uses special flags in its CommonJS and ESM distributions to facilitate tree shaking of code sections that are used for debugging. Tree shaking is a way to remove unused code in your application during the build process.
 
+<PlatformSection notSupported={["javascript.nextjs"]}>
 To mark any debug code as unused, you must replace debug flags in the Sentry SDK with `false`. We've outlined examples of how to do this in popular toolchains below.
+</PlatformSection>
+
+<PlatformSection notSupported={["javascript.nextjs"]}>
 
 ### Tree Shaking Debug Code With webpack
 
@@ -428,6 +432,10 @@ module.exports = {
 };
 ```
 
+</PlatformSection>
+
+<PlatformSection notSupported={["javascript.nextjs"]}>
+
 ### Tree Shaking Debug Code With rollup.js
 
 If you're using rollup.js, we recommend [rollup's replace plugin](https://www.npmjs.com/package/@rollup/plugin-replace) to replace all occurrences of `__SENTRY_DEBUG__` with `false`:
@@ -451,6 +459,8 @@ export default {
 };
 ```
 
+</PlatformSection>
+
 <PlatformSection supported={["javascript.nextjs"]}>
 
 ### Tree Shaking Debug Code With Next.js