You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See #4186 where we worked through remove all other export * from ... usage in published packages. These in the sdk-node package are the last remaining ones:
See #4186 where we worked through remove all other
export * from ...
usage in published packages. These in thesdk-node
package are the last remaining ones:opentelemetry-js/experimental/packages/opentelemetry-sdk-node/src/index.ts
Lines 20 to 27 in e7865c6
The original motivations for remove
export *
usage:Some discussion specifically about the
export *
in the sdk-node package start here: #4186 (comment)Does anyone use these re-exports?
Some anecdotal data on how common it is that these re-exports are used from the
sdk-node
package.The contrib repo has three cases of using these re-exports:
The first one (in auto-instrumentations-node) will be removed as part of #5443 and open-telemetry/opentelemetry-js-contrib#2708).
I acknowledge the convenience of using the
tracing
re-export to get common classes liketracing.SimpleSpanProcessor
andtracing.ConsoleSpanExporter
.An unscientific read through results from https://github.com/search?q=%22from+'%2540opentelemetry%252Fsdk-node'%22 suggests that somewhere around 10% of hits for
import { ... } from '@opentelemetry/sdk-node'
are using one of these re-exports.The text was updated successfully, but these errors were encountered: