Avoided using global scope for require variable

Now requiring the require instance rather than using global scope

v0.7.4

• pass template document along when rendering a template source (helps in multi-window scenarios)

v0.7.3

• Fix an issue with the afterRender function not firing when changing from an empty template name to a valid template name

v0.7.2

Allow the option of passing a string for afterRender which corresponds to a method on the resolved module

v0.7.1

• look for window.requirejs before window.require to avoid any conflicts (like node's require in a node-webkit project)

v0.7.0

• support templateProperty module option that allows using a template defined in a property on the module (self-contained module/template). Can also specify globally ko.bindingHandlers.module.templateProperty.
• ensure that valueAccessor() is called later so that in KO 3.0+ observables/computed accessed in the binding string name: 'mymodule-' + mode() would be captured as dependencies.
• update references to use KO 3.1

v0.6.2

• allow afterRender function to be successfully defined later when passing an observable to module binding with an initial value of null/undefined.

v0.6.1

-afterRender is only called after the template is actually ready rather than initially and then when the template is available
-upgrade to Jasmine 2.0 for unit tests
-update references to use KO 3.0.

v0.6.0

Added the ability to customize the name of the text plugin that is used. This defaults to "text" and can be customized by setting ko.amdTemplateEngine.defaultRequireTextPluginName.

v0.5.2

• avoid dependencies in disposal check, even if triggered by dom node disposal