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 created to be very "atomic" for each case, but I think some improvement will do.
If you're interested you can lead the effort and propose your contribution to gather some acceptance (first) and then propose how to bring that to Royale. Then try to work on a branch and ask for help when needed. Thanks El mar., 8 oct. 2019 a las 10:00, Chris Velevitch (< [email protected]>) escribió: > 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 compilation > pipeline that feeds into Webpack to create the final compacted > distributable app. > > > > [1] https://webpack.js.org/guides/tree-shaking/ > -- Carlos Rovira http://about.me/carlosrovira
