Preparing to split out the UIZE Web site code from the UIZE core code, so that the UIZE Web site is an app built using UIZE.
It's now possible to get the UIZE modules from a separate Web site project using UIZE, given the right config value for the uizePath option.
Order is actually important here, because the urlMatcher for built modules catches the URLs for built library modules, but clearly different handling is needed. So, the handler for built library modules must be invoked first.
Added URL transformer methods to have comprehensive coverage of all combinations of two differing, for consistency.
More refactoring of file builder adapter.
D'OH!
Starting a sample site that can be used by developers to better understand how to use UIZE in their own projects.
Need to go back one directory to get build.js file.
Don't want console.logs hanging outstaying their welcome.
Unprocessed files is more correct than static files, and this build script is generic enough to be in the Uize namespace.
Function wasn't in use anymore, since that logic was migrated into the sourceUrlFrom*Url instance methods of the file builder adapter.
Got this script to build the UIZE modules for projects other than the UIZE Web site.
Got this script to copy over the unprocessed files from the UIZE modules folder for projects other than the UIZE Web site.