Access other packages from WASM modules

Hello. First, you should post this as an idea and have it upvoted. That’s how
we review and prioritize third party developers feature request. @Paavo Part
of the need you describe would be covered by an API to request airport and nav
data I think ( ) As for
retrieving local vars from other packages to be able to write to it, I’d say
it’s up to the package creator to document which local vars he wants to
expose. @BenBaron85 I’m not sure to understand what you want to do with data
from other packages manifest.json, could you elaborate on that? I’d be
interested to know more concrete examples of usage to be able to judge if
those request can be addressed a different way or if some of them really
require a WASM access to other packages. Regards, Sylvain