jgranick commented on issue #232: (Feature Request) Support for JS extern 
output with royale-js
URL: https://github.com/apache/royale-asjs/issues/232#issuecomment-389910412
   Yeah, I think it makes sense to allow both, for example, allowing 
"node_modules/openfl/lib" as a source path vs. 
"node_modules/openfl/dist/openfl.swc" as an external library path, is similar 
to how we allow ES6/TypeScript developers to either use `require` (which comes 
from "lib" as separate modules) or to require/import a precompiled "openfl.js" 
or "openfl.min.js" which comes from "dist".
   I apologize in advance for fitting a couple new questions within this one 
issue, but I have a couple questions that are somewhat related that I could not 
find documentation about.
   After my SWC created, where do I put my source files? Can I give a compiler 
argument to specify where external JS files are located? Can I use `require` 
instead of using `window` references? Can this work with CommonJS-style modules 
(`var openfl_display_Sprite = require 
("../path/openfl/display/Sprite").default`)? Is there a way to avoid using 
"bin/js-debug" and "bin/js-release" (to customize the output directory)? 
Warnings about public variables and minification prints as a warning, but seems 
to emit an error code and stop my compilation. Can I ignore this warning, or do 
something automatic to "keep" a variable?
   Thank you

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:

With regards,
Apache Git Services

Reply via email to