These experimental modules had strict mode compliance issues that went undetected in the migration to using strict mode.
The file builder functionality is now expressed through a service interface. This makes it possible to have project specific adapters, which allows us to write things like the Web server code to a generic file builder interface, where different site projects will have different adapters for this service. To this end, _build.js and env.json have been modified to allow the services setup to be configured. The UIZE Web site uses its own service setup module that sets its adapter for the file builder service.
Factored out getJsModules and getIndexableFiles methods from UizeSite.Build.File into a new UizeSite.Build.Util modules, so that these modules can be accessed in a more reasonable way by the UizeSite.Build.Files.* modules.
Fixed typos.
Factored out the jsModuleExtensionRegExp regular expression.
Since the file builder functionality has been turned into service, the name perform for the main method is no longer necessary and is actually a bit cryptic, so it gets renamed to buildFile.
Since the project has been restructured, it's no longer all that meaningful (and it seems kinda silly) that the build catalyst script is prefixed with an underscore. Renaming.