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
When using the following library (@unovis/ts) inside of an esbuild bundle, a number of modules that are imported by various components are not properly tree-shaken when code splitting is enabled. When code splitting is disabled, the modules are correctly discarded.
As far as I can tell this is primarily caused by the bare import in @unovis/ts/index.js that leads to the (one of many) following chain:
Repro: https://github.com/taylorzane/esbuild-elkjs-bundle (includes bundle output and metafiles)
When using the following library (
@unovis/ts
) inside of an esbuild bundle, a number of modules that are imported by various components are not properly tree-shaken when code splitting is enabled. When code splitting is disabled, the modules are correctly discarded.As far as I can tell this is primarily caused by the bare import in
@unovis/ts/index.js
that leads to the (one of many) following chain:It's not immediately clear whether the underlying problem is with esbuild or the library, but the discrepancy between splitting/no splitting is odd.
The text was updated successfully, but these errors were encountered: