Add event procesor adding request data to event

Author: Luca Forstner

packages/nextjs/src/config/wrappers/wrapperUtils.ts

@@ -1,4 +1,5 @@
-import { captureException } from '@sentry/core';
+import { captureException, getCurrentHub, startTransaction } from '@sentry/core';
+import { addRequestDataToEvent } from '@sentry/node';
 import { getActiveTransaction } from '@sentry/tracing';
 import { Transaction } from '@sentry/types';
 import { fill } from '@sentry/utils';
@@ -103,6 +104,16 @@ export function callTracedServerSideDataFetcher<F extends (...args: any[]) => Pr
     const currentScope = getCurrentHub().getScope();
     if (currentScope) {
       currentScope.setSpan(dataFetcherSpan);
+      currentScope.addEventProcessor(event =>
+        addRequestDataToEvent(event, req, {
+          include: {
+            // When the `transaction` option is set to true, it tries to extract a transaction name from the request
+            // object. We don't want this since we already have a high-quality transaction name with a parameterized
+            // route. Setting `transaction` to `true` will clobber that transaction name.
+            transaction: false,
+          },
+        }),
+      );
     }
 
     try {

packages/nextjs/src/index.client.ts

@@ -11,8 +11,6 @@ export * from '@sentry/react';
 export { nextRouterInstrumentation } from './performance/client';
 export { captureUnderscoreErrorException } from './utils/_error';
 
-export { withSentryGetInitialProps } from './config/wrappers';
-
 export { Integrations };
 
 // Previously we expected users to import `BrowserTracing` like this: