Quite simply, the modular-js generator will output AMD modules for each class in your Haxe application. The filename is generated from the parent package of each class.
- Install modular-js with haxelib
haxelib install modular-js
- Add the generator in your HXML file.
-lib modular-js
- You must specify all of the classes of all the dynamic entry points in your hxml file. This tells the compiler to consider each class for Dead Code Elimination when outputting the files of the Haxe Standard Library.
- Why would you do this?
There are many good reasons to split your project into modules.
- The vast majority of websites have multiple entry-points (web pages). Javascript modules allow you to share code between these entry-points, with existing code and with web-workers.
- There is less code to push to the browser when you publish updates.
- Debugging is easier because files are logically separated.
- Processing your Javascript is easier with tools like Webpack or Browserify.
- Won't loading multiple files make my website slower?
In short, no. The longer answer is, if your server is configured to use SPDY or HTTPS2 and your target browser audience supports one of them, then the slow-down caused by multiple files is not even worth mentioning. To learn more about techniques of making your website load quickly, watch Jake Archibald's talk here.
- Using
-debugwill not generate source-maps. (But the javascript output is uncompressed and very readable so fixing this is a low priority.)
- ES6 Modules
- CommonJS Modules