@adobe/alloy-node 0.2.0-beta.0 → 0.2.1-beta.0
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@adobe/alloy-node",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.1-beta.0",
|
|
4
4
|
"description": "Adobe Experience Platform Web SDK - Node.js entrypoint",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"repository": {
|
|
@@ -24,7 +24,7 @@
|
|
|
24
24
|
}
|
|
25
25
|
},
|
|
26
26
|
"dependencies": {
|
|
27
|
-
"@adobe/alloy-core": "^1.3.
|
|
27
|
+
"@adobe/alloy-core": "^1.3.1-beta.0"
|
|
28
28
|
},
|
|
29
29
|
"scripts": {
|
|
30
30
|
"typecheck": "tsc -p jsconfig.json"
|
|
@@ -14,7 +14,9 @@ governing permissions and limitations under the License.
|
|
|
14
14
|
|
|
15
15
|
/**
|
|
16
16
|
* Node has no `navigator.sendBeacon`, so there is no separate unload-safe
|
|
17
|
-
* transport — both network strategies use `fetch`.
|
|
17
|
+
* transport — both network strategies use `fetch`. For the same reason the
|
|
18
|
+
* `keepalive` option of `sendFetchRequest` is ignored: there is no page to
|
|
19
|
+
* unload.
|
|
18
20
|
*
|
|
19
21
|
* @param {Object} [options]
|
|
20
22
|
* @param {Record<string, string>} [options.headers] Extra headers merged
|