ref(nestjs): Use @sentry/conventions

Source span/attribute keys from `@sentry/conventions` instead of the
previous OpenTelemetry / vendored convention constants. No functional change.

Includes the shared `vite/vite.config.ts` and `packages/typescript/tsconfig.json`
infra changes needed for the vendored package across supported Node versions.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: mydea

packages/nestjs/package.json

@@ -46,13 +46,13 @@
   "dependencies": {
     "@opentelemetry/api": "^1.9.1",
     "@opentelemetry/instrumentation": "^0.214.0",
-    "@opentelemetry/semantic-conventions": "^1.40.0",
     "@sentry/core": "10.57.0",
     "@sentry/node": "10.57.0"
   },
   "devDependencies": {
     "@nestjs/common": "^10.0.0",
     "@nestjs/core": "^10.0.0",
+    "@sentry/conventions": "^0.11.0",
     "reflect-metadata": "^0.2.2",
     "rxjs": "^7.8.2"
   },

packages/nestjs/rollup.npm.config.mjs

@@ -3,5 +3,12 @@ import { makeBaseNPMConfig, makeNPMConfigVariants } from '@sentry-internal/rollu
 export default makeNPMConfigVariants(
   makeBaseNPMConfig({
     entrypoints: ['src/index.ts', 'src/setup.ts'],
+    packageSpecificConfig: {
+      output: {
+        // keep emitted module paths relative to `src` so the bundled `@sentry/conventions`
+        // (a devDependency, vendored into the build) doesn't shift the output layout
+        preserveModulesRoot: 'src',
+      },
+    },
   }),
 );

packages/nestjs/src/integrations/vendored/instrumentation.ts

@@ -26,7 +26,7 @@ import {
   InstrumentationNodeModuleFile,
   isWrapped,
 } from '@opentelemetry/instrumentation';
-import { ATTR_HTTP_ROUTE } from '@opentelemetry/semantic-conventions';
+import { HTTP_ROUTE } from '@sentry/conventions/attributes';
 import { SDK_VERSION } from '@sentry/core';
 import { AttributeNames, NestType } from './enums';
 
@@ -174,7 +174,7 @@ function createWrapCreateHandler(tracer: api.Tracer, moduleVersion: string | und
           ...NestInstrumentation.COMMON_ATTRIBUTES,
           [AttributeNames.VERSION]: moduleVersion,
           [AttributeNames.TYPE]: NestType.REQUEST_CONTEXT,
-          [ATTR_HTTP_ROUTE]: req.route?.path || req.routeOptions?.url || req.routerPath,
+          [HTTP_ROUTE]: req.route?.path || req.routeOptions?.url || req.routerPath,
           [AttributeNames.CONTROLLER]: instanceName,
           [AttributeNames.CALLBACK]: callbackName,
         };

packages/typescript/tsconfig.json

@@ -18,6 +18,9 @@
     "strict": true,
     "strictBindCallApply": false,
     "target": "es2020",
-    "noUncheckedIndexedAccess": true
+    "noUncheckedIndexedAccess": true,
+    "paths": {
+      "@sentry/conventions/attributes": ["../../node_modules/@sentry/conventions/dist/attributes"]
+    }
   }
 }

vite/vite.config.ts

@@ -5,6 +5,16 @@ export default defineConfig({
     __DEBUG_BUILD__: true,
   },
   test: {
+    server: {
+      deps: {
+        // `@sentry/conventions` is vendored into our build output (under `build/esm/node_modules/...`)
+        // as ESM `.js` files. Vitest externalizes anything under a `node_modules/` path and loads it via
+        // native `require`, which fails on Node 18 ("ES Module shipped in a CommonJS package") because
+        // Node <20.19 can't `require()` ESM. Inlining makes Vitest transform it instead, so it works on
+        // all supported Node versions. Production is unaffected (the package resolves via its exports map).
+        inline: [/@sentry[/\\]conventions/],
+      },
+    },
     coverage: {
       enabled: true,
       reportsDirectory: './coverage',

yarn.lock

@@ -7578,6 +7578,11 @@
     "@sentry/cli-win32-i686" "2.58.6"
     "@sentry/cli-win32-x64" "2.58.6"
 
+"@sentry/conventions@^0.11.0":
+  version "0.11.0"
+  resolved "https://registry.yarnpkg.com/@sentry/conventions/-/conventions-0.11.0.tgz#5a324b8368dc5c141260bd8ccc684756ea3dd843"
+  integrity sha512-AQTAKeq9mDpOElDFSPymZTPZF/c50rk355mWTf5Y1ZxZJKKOBli5qTttskJyCxrE5ynNgN1KwcXoU5MRrMSRmQ==
+
 "@sentry/node-cpu-profiler@^2.4.2":
   version "2.4.2"
   resolved "https://registry.yarnpkg.com/@sentry/node-cpu-profiler/-/node-cpu-profiler-2.4.2.tgz#d0ba01370545297d015df1497daf7f81e27f2ab5"