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
Hey!
Right now rollup seems to reset module namespace every time the file is executed as seen in this example((this.myBundle = {})). This is problematic when you have multiple packages that should exist in common namespace inside window object, but some of them are lazy loaded when rarely needed. In this situation the variable will be cleared every time dynamic bundle is included.
The solution would be to slightly change the code so the generated piece would look like: (this.myBundle = this.myBundle || {}).
The text was updated successfully, but these errors were encountered:
krzksz
changed the title
Use existing moduleName object for IIFE if present.
Use existing moduleName object for IIFE if present
Feb 3, 2016
krzksz
changed the title
Use existing moduleName object for IIFE if present
Use existing moduleName object for IIFE and UMD if present
Feb 7, 2016
krzksz
pushed a commit
to krzksz/rollup
that referenced
this issue
Feb 7, 2016
Hey!
Right now rollup seems to reset module namespace every time the file is executed as seen in this example(
(this.myBundle = {})
). This is problematic when you have multiple packages that should exist in common namespace inside window object, but some of them are lazy loaded when rarely needed. In this situation the variable will be cleared every time dynamic bundle is included.The solution would be to slightly change the code so the generated piece would look like:
(this.myBundle = this.myBundle || {})
.The text was updated successfully, but these errors were encountered: