Cannot find package .../@opentelemetry\semantic-conventions\index.js

[skoenfaelt]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Self-hosted/on-premise

Which SDK are you using?

@sentry/nuxt

SDK Version

9.17.0

Framework Version

3.17.2

Link to Sentry event

No response

Reproduction Example/SDK Setup

fresh install no custom config other than the self hosted server
https://github.com/skoenfaelt/sentry-deploy-bug/tree/main

Steps to Reproduce

1. build your project with sentry setup
2. open this folder path .output\server\node_modules\@sentry\node\node_modules\@opentelemetry\semantic-conventions
3. 'index.js' is not present.

Full Error Log (hidden user path)
node:internal/modules/esm/resolve:215
const resolvedOption = FSLegacyMainResolve(packageJsonUrlString, packageConfig.main, baseStringified);
^

Error: Cannot find package '...\server\node_modules@sentry\node\node_modules@opentelemetry\semantic-conventions\index.js' imported from ...\server\node_modules@sentry\node\build\esm\integrations\tracing\koa.js
at legacyMainResolve (node:internal/modules/esm/resolve:215:26)
at packageResolve (node:internal/modules/esm/resolve:841:14)
at moduleResolve (node:internal/modules/esm/resolve:927:18)
at defaultResolve (node:internal/modules/esm/resolve:1169:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:542:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:510:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:239:38)
at ModuleWrap. (node:internal/modules/esm/module_job:96:40)
at link (node:internal/modules/esm/module_job:95:36) {
code: 'ERR_MODULE_NOT_FOUND'
}

Node.js v20.18.0

---

"dependencies": {
    // ...
    "@sentry/nuxt": "^9.17.0",
    "nuxt": "^3.17.2",
    "vue": "^3.5.13",
    "vue-router": "^4.5.1"
  },
  "overrides": {
    "@vercel/nft": "^0.27.4"
  }

Expected Result

I assume that the website is loading.

Actual Result

The website is not loading, creating an error log.
If I run the proj build locally in my proj folder it runs. As soon as I copy the contents of the .output folder to my IIS its not working anymore. I assume its working locally because the whole node_modules are present.

I also have removed my node_modules folder and my bun.lock > fresh install without cache bun i --no-cache

could linked to #15628 (comment)

[s1gr1d]

Hello, can you provide a small reproduction example?

And which package manager do you use?

[skoenfaelt]

Hello @s1gr1d

please checkout
https://github.com/skoenfaelt/sentry-deploy-bug/tree/main

In this example I use npm.
The proj context

1. created a fresh nuxt app via npm create nuxt@latest
2. npx @sentry/wizard@latest -i nuxt

I do not know how to create logs locally, but thats basically what I did with my real project.

in this example I expect at least the app to start. Sentry wont work, since you can not reach our self hosted url from outside.

!Important
please copy the contents of .output in a folder somewhere else than the proj folder and try to start the prod server. then the error will show immediatly

remove adjust the path (.output) according to your context.

node .output/server/index.mjs // official starter of prod server
node --import ./.output/server/sentry.server.config.mjs .output/server/index.mjs // from docs of sentry

Both start commands behave the same > error

[s1gr1d]

Hello, thanks for the reproduction! I just tried it and was not able to reproduce the issue.

In the app directory of your server there is no node_modules folder, so remove it here locally to behave the same.

I read this comment in the readme of your reproduction and wanted to ask why you would remove the node_modules that are created in .output/server? Also without Sentry, the server would need those node_modules in order to work. Or do you have a special setup which includes bundling your server output?

[skoenfaelt]

sorry for being unclear.

in dev mode, you will install your node_modules in your project.
then you start developing.

My reproduction of the readme was a bit unclear as i recognized it later. Forget deleting those dev node_modules. If you copy the .output folder somewhere else, desktop for example and you open the folder in a terminal, starting the prod server the error should occur.

If you start the prod server from the .output folder inside your project, then the server/.../node_modules will reference the node_modules from your project (npm i)
this is not the case in the real world. the prod server does not know our nodee_modules. Its correct to have the server/.../node_modules.

The issue is that there is no index.js in "server\node_modules@sentry\node\node_modules@opentelemetry\semantic-conventions\index.js"