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
This one might be a little tricky, we have multiple levels of side-effectual modules. I want to avoid preventing rollup from doing its dead code eliminate by having a blanket rule of keeping code when there are no side-effects just it is imported like import "foo"; but this might require that. Still investigating.
This is an internal decision to rollup, which we can't really control. Even if we could I'm not sure that we should, just for this use case. Promoting dependencies to parent modules is good in most situations as it means the removal of a module (cc/vendor in this case).
Unfortunately this doesn't play well with the sideBundle feature. So I'm not sure what to do about this. sideBundle's sort of a weird feature, it lets you control how splitting works and that's not something steal-tools ever really did before.
see this demo app https://github.com/pYr0x/sidebundle
if treeshaking is off,
vendor
gets bundles outif true,
vendor
is not bundledThe text was updated successfully, but these errors were encountered: