aharui commented on issue #232: (Feature Request) Support for JS extern output with royale-js URL: https://github.com/apache/royale-asjs/issues/232#issuecomment-389385188 You are correct that an extern represents code that exists at runtime. However, in Royale, the fact that some code is going to be supplied at runtime is only important to the Google Closure Compiler that optimizes the final set of JS. The extern in AS helped the compiler resolve the APIs you used, but we still need to convert it to the format that Google expects which is essentially a JS file. Since it probably doesn't make sense for consumers of your library to have the AS extern compiled to JS on every compile, it is probably better to transpile the AS to JS and package both into a SWC so the AS remains paired with its transpiled JS counterpart. I was thinking you wanted to make development of the AS extern easier by skipping the creating of the SWC and paying the price of the transpile on each compile until your errors go away and then you can put it all in a SWC. If you want to make sure that workflow is valid I will look into it.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
