Build & Unit Test Scripts Improvements

[BenAtZazzle]

So we are trying to split out our JS into global JS (Uize modules + a set of common Zazzle modules) and application-specific JS. These two groups of JS would live in two separate directories. The problem we're running into is that the build scripts, the unit tests scripts, and a few other scripts assume that all the JS modules live in a single directory and are built into a single directory.

At the source is the _build-env.json file that defines buildFolderPath and moduleFolderPath (and is used in _build-script-setup.js). Instead of being strings, we would need them to be functions that would take as a parameter the module and then return a string which is the folder path to the module.

In doing a cursory investigation, the actual modules effected would be:

• Uize.Wsh.AutoScruncher
• Uize.Wsh.BuildUtils
• Uize.Wsh.CompileJstModules
• Uize.Wsh.NeatenJsFiles

And of course, in addition to these modules, would be any other scripts that write moduleLoader code.

And while we're on the topic of separate directories, it would be nice to have all those Uize.Wsh.* files separated from the actual web code so we don't have to deploy those to our web server. Not nearly as important, but a nice-to-have.

Thanks!

[BenAtZazzle]

This problem has changed somewhat now that the build process has been dramatically upgraded.

The problem has been slightly fixed in that now there's a path to Uize modules and a path to other modules, but the Zazzle set up is such that we need 3 locations because we group Uize with the set of common Zazzle modules.

With the new system, it seems like build.js needs to be able to take some sort of namespace dictionary mapping to determine where to look for the module which can be specified in uize-config.json.