@dosgato/templating 0.0.100 → 0.0.101
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/provider.d.ts +15 -0
- package/package.json +1 -1
package/dist/provider.d.ts
CHANGED
|
@@ -81,6 +81,21 @@ export interface JSBlock {
|
|
|
81
81
|
* (unless their dependents are smart enough to wait for the global to be defined).
|
|
82
82
|
*/
|
|
83
83
|
async?: boolean;
|
|
84
|
+
/**
|
|
85
|
+
* Do not treat this script like a module
|
|
86
|
+
*
|
|
87
|
+
* By default we set the `type="module"` attribute on script tags. Mostly what this will do is ensure
|
|
88
|
+
* your top-level variables don't accidentally pollute the global scope. You would need to do
|
|
89
|
+
* `window.myVar =` instead of `const myVar =`.
|
|
90
|
+
*
|
|
91
|
+
* If your script is full of intentional globals and you don't want to refactor it, you can set
|
|
92
|
+
* this to false.
|
|
93
|
+
*
|
|
94
|
+
* This is also useful for frameworks like jQuery or prototype to ensure that they are executed
|
|
95
|
+
* immediately instead of just before DOMContentLoaded. jQuery in particular behaves poorly when
|
|
96
|
+
* you combine `type="module"` or `defer` with jQuery(document).ready().
|
|
97
|
+
*/
|
|
98
|
+
nomodule?: boolean;
|
|
84
99
|
}
|
|
85
100
|
export interface FileDeclaration {
|
|
86
101
|
/**
|