feat(sdk-node)!: drop lazy-loading of jaeger exporter #5989
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
A whole bunch of bundlers (at least vite, and rollup, likely many more) are failing to build when
@opentelemetry/sdk-node
is used. The reason for it is that we try to lazy-load@opentelemetry/exporter-jaeger
if present, which we've marked as deprecated for a long time now. That exporter has been superseded by@opentelemetry/exporter-trace-otlp-http
et al. since Jaeger now has native support for OTLPThis PR removes the lazy-loading in favor of the OTLP exporter, which remains fully supported.
Though deprecated, the Jaeger exporter will continue to be published from this repo until we mark
@opentelemetry/exporter-trace-otlp-http
as stable.Fixes #4297