|
2 | 2 |
|
3 | 3 | 1. How can I file a bug report: |
4 | 4 |
|
5 | | - See our guidelines on [reporting issues](https://github.com/wycats/handlebars.js/blob/master/CONTRIBUTING.md#reporting-issues). |
| 5 | + See our guidelines on [reporting issues](https://github.com/handlebars-lang/handlebars.js/blob/master/CONTRIBUTING.md#reporting-issues). |
6 | 6 |
|
7 | 7 | 1. Why isn't my Mustache template working? |
8 | 8 |
|
9 | | - Handlebars deviates from Mustache slightly on a few behaviors. These variations are documented in our [readme](https://github.com/wycats/handlebars.js#differences-between-handlebarsjs-and-mustache). |
| 9 | + Handlebars deviates from Mustache slightly on a few behaviors. These variations are documented in our [readme](https://github.com/handlebars-lang/handlebars.js#differences-between-handlebarsjs-and-mustache). |
10 | 10 |
|
11 | 11 | 1. Why is it slower when compiling? |
12 | 12 |
|
|
36 | 36 | ```sh |
37 | 37 | handlebars --version |
38 | 38 | ``` |
| 39 | + |
39 | 40 | If using the integrated precompiler and |
40 | 41 |
|
41 | 42 | ```javascript |
42 | 43 | console.log(Handlebars.VERSION); |
43 | 44 | ``` |
| 45 | + |
44 | 46 | On the client side. |
45 | 47 |
|
46 | 48 | We include the built client libraries in the npm package for those who want to be certain that they are using the same client libraries as the compiler. |
47 | 49 |
|
48 | | - Should these match, please file an issue with us, per our [issue filing guidelines](https://github.com/wycats/handlebars.js/blob/master/CONTRIBUTING.md#reporting-issues). |
| 50 | + Should these match, please file an issue with us, per our [issue filing guidelines](https://github.com/handlebars-lang/handlebars.js/blob/master/CONTRIBUTING.md#reporting-issues). |
49 | 51 |
|
50 | 52 | 1. Why doesn't IE like the `default` name in the AMD module? |
51 | 53 |
|
52 | 54 | Some browsers such as particular versions of IE treat `default` as a reserved word in JavaScript source files. To safely use this you need to reference this via the `Handlebars['default']` lookup method. This is an unfortunate side effect of the shims necessary to backport the Handlebars ES6 code to all current browsers. |
53 | 55 |
|
54 | 56 | 1. How do I load the runtime library when using AMD? |
55 | 57 |
|
56 | | - There are two options for loading under AMD environments. The first is to use the `handlebars.runtime.amd.js` file. This may require a [path mapping](https://github.com/wycats/handlebars.js/blob/master/spec/amd-runtime.html#L31) as well as access via the `default` field. |
| 58 | + There are two options for loading under AMD environments. The first is to use the `handlebars.runtime.amd.js` file. This may require a [path mapping](https://github.com/handlebars-lang/handlebars.js/blob/master/spec/amd-runtime.html#L31) as well as access via the `default` field. |
57 | 59 |
|
58 | | - The other option is to load the `handlebars.runtime.js` UMD build, which might not require path configuration and exposes the library as both the module root and the `default` field for compatibility. |
| 60 | + The other option is to load the `handlebars.runtime.js` UMD build, which might not require path configuration and exposes the library as both the module root and the `default` field for compatibility. |
59 | 61 |
|
60 | 62 | If not using ES6 transpilers or accessing submodules in the build the former option should be sufficient for most use cases. |
0 commit comments