jeez

Author: Luca Forstner

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

@@ -82,7 +82,8 @@ To fix this, change the `tracePropagationTargets` option during SDK initializati
 </Expandable>
 </PlatformCategorySection>
 
-<PlatformCategorySection notSupported={['browser', 'javascript.aws-lambda', 'javascript.azure-functions', 'javascript.bun', 'javascript.cloudflare', 'javascript.deno', 'javascript.electron', 'javascript.gcp-functions']}>
+<PlatformCategorySection notSupported={['browser']}>
+<PlatformSection notSupported={['javascript.aws-lambda', 'javascript.azure-functions', 'javascript.bun', 'javascript.cloudflare', 'javascript.deno', 'javascript.electron', 'javascript.gcp-functions']}>
 <Expandable permalink title="Error: 'import-in-the-middle' failed to wrap">
  When using ESM, by default all packages are wrapped under the hood by
  [import-in-the-middle](https://www.npmjs.com/package/import-in-the-middle).
@@ -92,6 +93,7 @@ To fix this, change the `tracePropagationTargets` option during SDK initializati
 Check out the <PlatformLink to="/install/esm/#troubleshooting-instrumentation">ESM Troubleshooting Instrumentation</PlatformLink> section for more information.
 
 </Expandable>
+</PlatformSection>
 </PlatformCategorySection>
 
 <PlatformCategorySection supported={['browser']}>