If the whole point of PAYG is to eliminate unused code from being
included in the final app distribution, then I'd like to suggest that
we take advantage of the tools the JavaScript ecosystem already has
for eliminating unused code.
I think we should take a look at Webpack [1] and create a compila
Hi Chris,
I think that will be a good addition and can complement PAYG in our current
state.
While PAYG and Strands and Beads give users the power to choose one code
and avoid other, Some code can still have vars or functions unused in some
cases.
With PAYG this will be very few, since the code is
It is worth mentioning that Royale uses Google's Closure compiler when
creating release builds. Closure compiler does very advanced JavaScript
code analysis that eliminates unused code from the final output, so it has
a very similar effect to tree shaking.
The ability to integrate into a webpack b
The compiler is theoretically designed to allow for different Emitters and
Publishers that can output different JS to support other module and
minification systems. Volunteers are welcome to work on those.
However, the Strands and Beads idea is not about minification for Google
Closure or WebP