There is a small typo in test/mustache-spec-test.js.

Should read `skipped` rather than `skiped`.

Because it seems the standard library for v0.21 that was used in the
usage tests before has been removed, it returns 404 now..

These changes optimizes the performance of escaping number
values, by not passing them through the ordinary HTML escaping
that is done on string values.

If the key is false or empty

Windows shell does not recognize 'single quotes' the same way as bash. The 'single quotes' in the build command have been changed to "double quotes" instead.

The linter enforces 'single quotes' but two strings in this test file were written using "double quotes". This issue was causing tests to fail.

If an object is provided for what used to be the `tags` argument instead of an array, then the object is treated as a "config" object. A config object can have a `tags` attribute which behaves the same as the `tags` argument, and it can also optionally have an `escape` argument that is used for providing a custom escape function for that render call. The rationale for this addition is that providing an escape function here, when rendering a template, is a safer pattern for specifying an escape function than modifying the global mustache.escape attribute when a project may need to use mustache to render more than just one kind of content, e.g. both HTML and Latex templates in the same project.

The `render` argument passed to a `function (text, render)` lambda function was not accounting for custom tags or other configuration. This issue has been fixed and a regression test has been added for this case.