These are chat archives for ractivejs/ractive
forEachinitially then manually optimize using
applyon this end, and usually
argumentson the other end (if spreading).
a.bar.baz. hoist-props will take all of your property accesses in a scope, turn them into shared strings if they meet a heuristic (actually saves space), and you end up with something like
var b='bar',c='baz';, which is also considered for each prop, so you end up only hoisting props that are used a ton or that are used a few times and are huge