support treeshaking to reduce bundle size for web project ?

[echoontheway]

it seems otel grows bigger and bigger, perhaps we can add an es entry like module in package.json

• This only affects the JavaScript OpenTelemetry library
• This may affect other libraries, but I would like to get opinions here first

[jessebond2]

I'd like to second this request. I'm profiling the impact on our production build and noticing that adding a number of opentelemetry packages is adding roughly 60kb~ to the final build, which is really large. It will have a negative impact on frontend performance...

[vmarchaud]

@jessebond2 Could you please provide the list of otel dependencies you are using ? If you can also have the details of which package is the heaviest, that would help a lot !
For information: there are work done to ship ESM version (#2112) so components are better treeshaked (at least we hope)

[jessebond2]

Hey @vmarchaud, sorry for the delayed response. Here's the list of packages I tried using and the incremental size diffs each package added. This was from the output of our production webpack build.

I think otel/core added around 10KB~ but wasn't listed in the table

[pichlermarc]

We've enabled tree-shaking in #3329.
There's an ongoing effort to further improve over at https://github.com/open-telemetry/opentelemetry-sandbox-web-js/ 🙂