feat(otlp-transformer)!: introduce separate entry-points for OTLP serializers #5263
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?
This is the second-to-last breaking PR for
@opentelemetry/otlp-transformer
before marking the package as stable (#4582). This solves some issues with rollup, that warns even for code that is dead in the end-user's app. See #5096, #4987.This PR adds entry points for each signal, each signal gets an entry point for
protobuf
andjson
to address #5096 and #4987The new entrypoint structure is:
-
/signal
,/signal/protobuf
,singal/json
- experimental signals are prefixed by
experimental/
to allow us marking the package stable before the experimental signals are - the spec moves quicker than we do, so I expect there to always be one that is not stableCloses #5216
Closes #4584
Fixes #5096
Partially addresses #4987
Type of change
How Has This Been Tested?