@sentry/node depends on unused packages

[hitsthings]

Problem Statement

@opentelemetry version management is complicated already with the plethora of packages there, but Sentry depends on a bunch of additional modules I don't need, which in turn depend on further modules I don't need, which creates more dependency management problems. Downloading excess packages is bad for my hard drive, the environment, npm install time, cold start time, my sanity, etc.

Solution Brainstorm

Ideally, @sentry/node would not depend directly on e.g. @opentelemetry/instrumentation-ioredis. You could move it to an optionalDependencies and people could choose whether they want that integration or not. Same for fastify, express, kafka, hapi, graphql, ...

It already fails at runtime, so safety-wise, the benefit is limited for the current setup. It'd be great if it only failed if I actually attempted to include the expressIntegration() or fastifyIntegration() or whatever, rather than failing on startup for any missing dependency.

Product Area

APIs

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[hitsthings]

I guess peerDependencies would be better to not install by default. You can use peerDependenciesMeta to set them optional as well.

[s1gr1d]

Hello, I think your concerns are valid. We created an issue for a @sentry/node-core SDK here. Feel free to react with an emoji and subscribe to it.

Closing this as it is a duplicate.