hi @paulishca ,
Thanks a lot for your interest and help! We’ve just tested that and what it does is only set the variable Meteor.isModern = true in the client. So it says it’s “modern” but the bundle is still based on legacy.
We’re still searching in the code where the build of the bundle is done.
We’re not sure it’s going to be easy as all packages in /Users/fafafa/.meteor/packages do have different sources for :
web.cordova
web.browser
web.browser-legacy
web.cordova-legacy (yeah, that exists!)
which probably means the required change to build a modern-like bundle for cordova is deeper/wider than just changing one value somewhere.
we’ll get back as soon as we find something useful!