@sentry/node depends on unused packages #15278
Description
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