fix(node): Allow use of NodeClient without calling init (#11585)

This needs exporting so that the `NodeClient` can be used without
calling the Node `init`.

There is a lot called in the Node init that is a hard requirement for
the `NodeClient` to function. Should these not be called in the
constructor?

Author: timfish

dev-packages/e2e-tests/test-applications/node-exports-test-app/scripts/consistentExports.ts

@@ -14,6 +14,8 @@ const NODE_EXPORTS_IGNORE = [
   'default',
   // Probably generated by transpilation, no need to require it
   '__esModule',
+  // Only required from the Node package
+  'setNodeAsyncContextStrategy',
 ];
 
 const nodeExports = Object.keys(SentryNode).filter(e => !NODE_EXPORTS_IGNORE.includes(e));

packages/node/src/index.ts

@@ -37,9 +37,13 @@ export type { NodeOptions } from './types';
 
 export { addRequestDataToEvent, DEFAULT_USER_INCLUDES, extractRequestData } from '@sentry/utils';
 
-// These are custom variants that need to be used instead of the core one
-// As they have slightly different implementations
-export { continueTrace } from '@sentry/opentelemetry';
+export {
+  // These are custom variants that need to be used instead of the core one
+  // As they have slightly different implementations
+  continueTrace,
+  // This needs exporting so the NodeClient can be used without calling init
+  setOpenTelemetryContextAsyncContextStrategy as setNodeAsyncContextStrategy,
+} from '@sentry/opentelemetry';
 
 export {
   addBreadcrumb,