The reason for this update is that we need to update the entire addon community to babel6 in order to get the new modules that will eventually lead to tree shaking.
Alternatively, the addon could remain in 5.X as long as the runtime code in initializers and instance-initializers is deleted.
The reason for this update is that we need to update the entire addon community to babel6 in order to get the new modules that will eventually lead to tree shaking.
Alternatively, the addon could remain in 5.X as long as the runtime code in initializers and instance-initializers is deleted.