Repository navigation
Refactor build to use an hxml file #31
Description
Activity
If we use a temporary file, and utilise an NPM like https://www.npmjs.com/package/tmp, we will need to take care to handle any relative paths. It might be easier to create a temporary hxml file in the same directory, and just be careful to clean it up.
If the macro option works that would probably be cleanest though.
I have missed something, or
--eachand--nextwill do the job, about the multiple-js?
https://haxe.org/manual/compiler-usage-hxml.html@aliokan no, the loader supports only a single JS output, and we need to replace the output target to generate a the file in a temporary location. In a single output, having
-jsseveral times (once in the hxml and once as an override) isn't allowed - this is a shame.Reacted by Laurent DeketelaereWhy it is needed to replace the
-jspath?Is it possible that haxe-loader parses the input hxml and figure out and use the output path from there?
If the
-jstag is from a included hxml, the webpack output would be basically empty, e.g.:haxe build.hxmlbuild.hxml:
-cp src path.hxml -lib xxpath.hxml:
-js out.js@kevinresol the problem is that the HXML is usually also used for IDE autocomplete as-is, hence why it will usually have a
-jsotherwise Haxe completion doesn't work. It's very convenient to troubleshoot the build outside Webpack as well. But otherwise we want to completely hide the output.@jasononeil for HXML the paths are relative to the working directory, not the HXML location, so we wouldn't even have to fix the paths (remember they become literally compiler arguments).
Currently the build process parses the hxml file and generates arguments list for haxe compilation - this is verbose, doesn't scale well, and has subtle edge case issues (like
--macrowith quotes in them, see #28).Is it possible to use the hxml file as is?
It doesn't seem to be possible because we need to replace the JS output target and only a single
-jsis allowed - maybe using a macro could work? A macro could dynamically replace the output file without touching the hxmlOtherwise we could generate a temporary hxml file
It should include the original hxml content with just the JS output replaced. Other added arguments should still be added to the build command.