@@ -2159,68 +2159,6 @@ added:
2159
2159
An ESM loader hook returned without calling ` next() ` and without explicitly
2160
2160
signaling a short circuit.
2161
2161
2162
- <a id =" ERR_MANIFEST_ASSERT_INTEGRITY " ></a >
2163
-
2164
- ### ` ERR_MANIFEST_ASSERT_INTEGRITY `
2165
-
2166
- An attempt was made to load a resource, but the resource did not match the
2167
- integrity defined by the policy manifest. See the documentation for [ policy] [ ]
2168
- manifests for more information.
2169
-
2170
- <a id =" ERR_MANIFEST_DEPENDENCY_MISSING " ></a >
2171
-
2172
- ### ` ERR_MANIFEST_DEPENDENCY_MISSING `
2173
-
2174
- An attempt was made to load a resource, but the resource was not listed as a
2175
- dependency from the location that attempted to load it. See the documentation
2176
- for [ policy] [ ] manifests for more information.
2177
-
2178
- <a id =" ERR_MANIFEST_INTEGRITY_MISMATCH " ></a >
2179
-
2180
- ### ` ERR_MANIFEST_INTEGRITY_MISMATCH `
2181
-
2182
- An attempt was made to load a policy manifest, but the manifest had multiple
2183
- entries for a resource which did not match each other. Update the manifest
2184
- entries to match in order to resolve this error. See the documentation for
2185
- [ policy] [ ] manifests for more information.
2186
-
2187
- <a id =" ERR_MANIFEST_INVALID_RESOURCE_FIELD " ></a >
2188
-
2189
- ### ` ERR_MANIFEST_INVALID_RESOURCE_FIELD `
2190
-
2191
- A policy manifest resource had an invalid value for one of its fields. Update
2192
- the manifest entry to match in order to resolve this error. See the
2193
- documentation for [ policy] [ ] manifests for more information.
2194
-
2195
- <a id =" ERR_MANIFEST_INVALID_SPECIFIER " ></a >
2196
-
2197
- ### ` ERR_MANIFEST_INVALID_SPECIFIER `
2198
-
2199
- A policy manifest resource had an invalid value for one of its dependency
2200
- mappings. Update the manifest entry to match to resolve this error. See the
2201
- documentation for [ policy] [ ] manifests for more information.
2202
-
2203
- <a id =" ERR_MANIFEST_PARSE_POLICY " ></a >
2204
-
2205
- ### ` ERR_MANIFEST_PARSE_POLICY `
2206
-
2207
- An attempt was made to load a policy manifest, but the manifest was unable to
2208
- be parsed. See the documentation for [ policy] [ ] manifests for more information.
2209
-
2210
- <a id =" ERR_MANIFEST_TDZ " ></a >
2211
-
2212
- ### ` ERR_MANIFEST_TDZ `
2213
-
2214
- An attempt was made to read from a policy manifest, but the manifest
2215
- initialization has not yet taken place. This is likely a bug in Node.js.
2216
-
2217
- <a id =" ERR_MANIFEST_UNKNOWN_ONERROR " ></a >
2218
-
2219
- ### ` ERR_MANIFEST_UNKNOWN_ONERROR `
2220
-
2221
- A policy manifest was loaded, but had an unknown value for its "onerror"
2222
- behavior. See the documentation for [ policy] [ ] manifests for more information.
2223
-
2224
2162
<a id =" ERR_MEMORY_ALLOCATION_FAILED " ></a >
2225
2163
2226
2164
### ` ERR_MEMORY_ALLOCATION_FAILED `
@@ -3436,6 +3374,100 @@ removed: v21.1.0
3436
3374
3437
3375
An import attribute is not supported by this version of Node.js.
3438
3376
3377
+ <a id =" ERR_MANIFEST_ASSERT_INTEGRITY " ></a >
3378
+
3379
+ ### ` ERR_MANIFEST_ASSERT_INTEGRITY `
3380
+
3381
+ <!-- YAML
3382
+ removed: REPLACEME
3383
+ -->
3384
+
3385
+ An attempt was made to load a resource, but the resource did not match the
3386
+ integrity defined by the policy manifest. See the documentation for policy
3387
+ manifests for more information.
3388
+
3389
+ <a id =" ERR_MANIFEST_DEPENDENCY_MISSING " ></a >
3390
+
3391
+ ### ` ERR_MANIFEST_DEPENDENCY_MISSING `
3392
+
3393
+ <!-- YAML
3394
+ removed: REPLACEME
3395
+ -->
3396
+
3397
+ An attempt was made to load a resource, but the resource was not listed as a
3398
+ dependency from the location that attempted to load it. See the documentation
3399
+ for policy manifests for more information.
3400
+
3401
+ <a id =" ERR_MANIFEST_INTEGRITY_MISMATCH " ></a >
3402
+
3403
+ ### ` ERR_MANIFEST_INTEGRITY_MISMATCH `
3404
+
3405
+ <!-- YAML
3406
+ removed: REPLACEME
3407
+ -->
3408
+
3409
+ An attempt was made to load a policy manifest, but the manifest had multiple
3410
+ entries for a resource which did not match each other. Update the manifest
3411
+ entries to match in order to resolve this error. See the documentation for
3412
+ policy manifests for more information.
3413
+
3414
+ <a id =" ERR_MANIFEST_INVALID_RESOURCE_FIELD " ></a >
3415
+
3416
+ ### ` ERR_MANIFEST_INVALID_RESOURCE_FIELD `
3417
+
3418
+ <!-- YAML
3419
+ removed: REPLACEME
3420
+ -->
3421
+
3422
+ A policy manifest resource had an invalid value for one of its fields. Update
3423
+ the manifest entry to match in order to resolve this error. See the
3424
+ documentation for policy manifests for more information.
3425
+
3426
+ <a id =" ERR_MANIFEST_INVALID_SPECIFIER " ></a >
3427
+
3428
+ ### ` ERR_MANIFEST_INVALID_SPECIFIER `
3429
+
3430
+ <!-- YAML
3431
+ removed: REPLACEME
3432
+ -->
3433
+
3434
+ A policy manifest resource had an invalid value for one of its dependency
3435
+ mappings. Update the manifest entry to match to resolve this error. See the
3436
+ documentation for policy manifests for more information.
3437
+
3438
+ <a id =" ERR_MANIFEST_PARSE_POLICY " ></a >
3439
+
3440
+ ### ` ERR_MANIFEST_PARSE_POLICY `
3441
+
3442
+ <!-- YAML
3443
+ removed: REPLACEME
3444
+ -->
3445
+
3446
+ An attempt was made to load a policy manifest, but the manifest was unable to
3447
+ be parsed. See the documentation for policy manifests for more information.
3448
+
3449
+ <a id =" ERR_MANIFEST_TDZ " ></a >
3450
+
3451
+ ### ` ERR_MANIFEST_TDZ `
3452
+
3453
+ <!-- YAML
3454
+ removed: REPLACEME
3455
+ -->
3456
+
3457
+ An attempt was made to read from a policy manifest, but the manifest
3458
+ initialization has not yet taken place. This is likely a bug in Node.js.
3459
+
3460
+ <a id =" ERR_MANIFEST_UNKNOWN_ONERROR " ></a >
3461
+
3462
+ ### ` ERR_MANIFEST_UNKNOWN_ONERROR `
3463
+
3464
+ <!-- YAML
3465
+ removed: REPLACEME
3466
+ -->
3467
+
3468
+ A policy manifest was loaded, but had an unknown value for its "onerror"
3469
+ behavior. See the documentation for policy manifests for more information.
3470
+
3439
3471
<a id =" ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST " ></a >
3440
3472
3441
3473
### ` ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST `
@@ -4016,7 +4048,6 @@ An error occurred trying to allocate memory. This should never happen.
4016
4048
[ domains ] : domain.md
4017
4049
[ event emitter-based ] : events.md#class-eventemitter
4018
4050
[ file descriptors ] : https://en.wikipedia.org/wiki/File_descriptor
4019
- [ policy ] : permissions.md#policies
4020
4051
[ relative URL ] : https://url.spec.whatwg.org/#relative-url-string
4021
4052
[ self-reference a package using its name ] : packages.md#self-referencing-a-package-using-its-name
4022
4053
[ special scheme ] : https://url.spec.whatwg.org/#special-scheme
0 commit comments