I saw that there's two devDependency entries old @opentelemetry/api-events and @opentelemetry/api-logs packages, which cause an old package to be present for these two packages.
The current version is actually specified as a dependency so removing the devDependency is safe.
Since the devDependency pulled in the local types, we had some type-mismatch with in @opentelemetry/sdk-logs where null was not an allowed input with the changed type.
Type of change
[x] Bug fix (non-breaking change which fixes an issue)
Which problem is this PR solving?
I saw that there's two
devDependency
entries old@opentelemetry/api-events
and@opentelemetry/api-logs
packages, which cause an old package to be present for these two packages.The current version is actually specified as a
dependency
so removing thedevDependency
is safe.Since the
devDependency
pulled in the local types, we had some type-mismatch with in@opentelemetry/sdk-logs
wherenull
was not an allowed input with the changed type.Type of change
How Has This Been Tested?