Adding code, tests and read me updates to support...

...the variables 'templatePath', 'localePath' and 'localeFileName' parameters. These parameters allow the developer to load their templates and locale files from a folder other than the default locations. This is valuable when creating two assemblies that use the exact same templates and locale files.

Some of the variables that were defined below are now moved up towards the top to make the error checking simpler to perform.

Also added some better error tracking if the Asset Manager fails to build the entire assembly. Errors are now output as a client-side call to console.error(). These error messages re prefaced with "Asset Manager build error:". This provides a simpler way for the developer to know WHY Asset Manager failed to build.


If the concern is ie.old, then it's simple enough to put a console check here and solve that problem. @dncrews would that resolve your concern, or do you feel fundamentally opposed to logging a message in the browser this way? A proper file can't be built, so the alternative is to return an empty file or some kind of error content. What would you propose instead?