Opentelemetry dependency too big for Firebase deploys

[ripperdoc]

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?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/node

SDK Version

10.5.0

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

I recently installed @sentry/node in a Firebase Functions Node project. Soon I found that I was no longer able to deploy to Firebase. The reason is that the total package including node_modules cannot be more than 500 MB uncompressed / 100 MB compressed.

I looked through the sizes in node_modules and can see that

184M    ./@opentelemetry/

Expected Result

This size is pretty unreasonable (which I guess is an issue with opentelemetry). I tried deleting it from node-modules but it won't run without it. I was hoping there was a way to avoid this dependency in Sentry, considering I'm not using neither opentelemetry nor any tracing.

Is there a way forward here or is Sentry not suitable for space-constrained Javascript environments?

Actual Result

See above

[linear]

JS-867 Opentelemetry dependency too big for Firebase deploys

[ripperdoc]

Hey, sorry to be that guy that find the resolution just after reporting, but I did find the https://www.npmjs.com/package/@sentry/node-core package now. My only ask would perhaps be to add a reference to that package to the start page of the Node.js (and equivalent) docs: https://docs.sentry.io/platforms/javascript/guides/node/

[andreiborza]

Hi @ripperdoc, if you're size constrained like that consider using @sentry/node-core. You'd have to set up the instrumentations you want to use yourself, we recommend at least getting @opentelemetry/instrumentation-http in addition.

edit: Ahh, too slow :).

It's on my plate to overhaul our docs and make node-core more prominent.