You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The console may wrap the output in quotes (`"`). If it does, ignore the quotes.
51
51
52
-
> You can read more about the `cjGetRuntimeResources`[here](/docs/reference/cjGetRuntimeResources).
53
-
54
52
### Step 2: Enable preloading in your integration
55
53
56
-
Update your `cheerpjInit` call to include the `preloadResources` option.
54
+
Update your [`cheerpjInit`](/docs/reference/cheerpjInit) call to include the [`preloadResources`](/docs/reference/cheerpjInit#preloadresources) option.
57
55
58
56
Example:
59
57
@@ -66,9 +64,7 @@ cheerpjInit({
66
64
});
67
65
```
68
66
69
-
Note that profiling the resources with `cjGetRuntimeResources()` and providing the result to `preloadResources` must be done in separate sessions. First, profile the application in one session to generate the list of resources. Then, in subsequent sessions, pass this list to `cheerpjInit` to enable preloading.
70
-
71
-
> You can read more about the `preloadResources` init option [here](/docs/reference/cheerpjInit#preloadresources).
67
+
Note that profiling the resources with [`cjGetRuntimeResources`](/docs/reference/cjGetRuntimeResources) and providing the result to [`preloadResources`](/docs/reference/cheerpjInit#preloadresources) must be done in separate sessions. First, profile the application in one session to generate the list of resources. Then, in subsequent sessions, pass this list to `cheerpjInit` to enable preloading.
0 commit comments