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 a dynamic import is removed via tree-shaking it leaves an undefined behind in the Bundle object that is passed to the generateBundle plugin hook. This seems unintended and can cause bugs in plugins that use that data like @modular-css/rollup.
Rollup Version: 1.1.0
Operating System (or Browser): Windows 10
Node Version: 10.12.0
How Do We Reproduce?
I made a gist. The README.md contains repro steps.
Expected Behavior
The Bundle object passed to generateBundle shouldn't have an undefined value inside of the dynamicImports array when a dynamic import is removed by tree-shaking.
Actual Behavior
The Bundle object passed to generateBundle has an undefined value inside of the dynamicImports array when a dynamic import is removed by tree-shaking.
The text was updated successfully, but these errors were encountered:
tivac
added a commit
to tivac/modular-css
that referenced
this issue
Jan 16, 2019
When a dynamic import is removed via tree-shaking it leaves an
undefined
behind in theBundle
object that is passed to thegenerateBundle
plugin hook. This seems unintended and can cause bugs in plugins that use that data like@modular-css/rollup
.How Do We Reproduce?
I made a gist. The
README.md
contains repro steps.Expected Behavior
The
Bundle
object passed togenerateBundle
shouldn't have anundefined
value inside of thedynamicImports
array when a dynamic import is removed by tree-shaking.Actual Behavior
The
Bundle
object passed togenerateBundle
has anundefined
value inside of thedynamicImports
array when a dynamic import is removed by tree-shaking.The text was updated successfully, but these errors were encountered: