-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Cannot find package .../@opentelemetry\semantic-conventions\index.js #16243
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hello, can you provide a small reproduction example? And which package manager do you use? |
Hello @s1gr1d please checkout In this example I use npm.
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 remove adjust the path (.output) according to your context.
Both start commands behave the same > error |
Hello, thanks for the reproduction! I just tried it and was not able to reproduce the issue.
I read this comment in the readme of your reproduction and wanted to ask why you would remove the |
sorry for being unclear. in dev mode, you will install your node_modules in your project. 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) The issue is that there is no index.js in "server\node_modules@sentry\node\node_modules@opentelemetry\semantic-conventions\index.js" |
So this error message is only occurring where you deploy your application? Can you share more information about your deployment environment? Where do you deploy it and how do you build and run the project there? |
If I start the prod server inside the project folder. No problem (i guess windows junction will reference the whole project node_moduels and not only those from the .output) Currently I deploy that sentry test app manually.
web.config
On Sentry Docs:
i did not use this command in local prod mode, i used Also with the adjusted command from docs its not working
|
@s1gr1d thank you for you diving into this problem! I tried a fresh installation on my private computer. same issue if you copy and paste the folder via windows context menu. and this works. Monday I will test this at the company, with the self hosted sentry. If this works with a copy powershell script, then I will close this issue. if this issue still perists I will ping you again, if its okay. For now, enjoy your weekend! |
Issue can be closed. Totally my fault by copy the demo app via windows copy/paste Solved by |
Is there an existing issue for this?
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
Steps to Reproduce
.output\server\node_modules\@sentry\node\node_modules\@opentelemetry\semantic-conventions
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
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)
The text was updated successfully, but these errors were encountered: