Skip to content

Commit 077fd72

Browse files
committed
lib,src: remove --experimental-policy
1 parent d545984 commit 077fd72

File tree

89 files changed

+22
-6127
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

89 files changed

+22
-6127
lines changed

benchmark/policy/policy-startup.js

Lines changed: 0 additions & 51 deletions
This file was deleted.

doc/api/cli.md

Lines changed: 0 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -879,14 +879,6 @@ following permissions are restricted:
879879
* Child Process - manageable through [`--allow-child-process`][] flag
880880
* Worker Threads - manageable through [`--allow-worker`][] flag
881881

882-
### `--experimental-policy`
883-
884-
<!-- YAML
885-
added: v11.8.0
886-
-->
887-
888-
Use the specified file as a security policy.
889-
890882
### `--experimental-require-module`
891883

892884
<!-- YAML
@@ -1518,18 +1510,6 @@ unless either the `--pending-deprecation` command-line flag, or the
15181510
are used to provide a kind of selective "early warning" mechanism that
15191511
developers may leverage to detect deprecated API usage.
15201512

1521-
### `--policy-integrity=sri`
1522-
1523-
<!-- YAML
1524-
added: v12.7.0
1525-
-->
1526-
1527-
> Stability: 1 - Experimental
1528-
1529-
Instructs Node.js to error prior to running any code if the policy does not have
1530-
the specified integrity. It expects a [Subresource Integrity][] string as a
1531-
parameter.
1532-
15331513
### `--preserve-symlinks`
15341514

15351515
<!-- YAML
@@ -2659,7 +2639,6 @@ one is included in the list below.
26592639
* `--experimental-modules`
26602640
* `--experimental-network-imports`
26612641
* `--experimental-permission`
2662-
* `--experimental-policy`
26632642
* `--experimental-print-required-tla`
26642643
* `--experimental-require-module`
26652644
* `--experimental-shadow-realm`
@@ -2703,7 +2682,6 @@ one is included in the list below.
27032682
* `--openssl-legacy-provider`
27042683
* `--openssl-shared-config`
27052684
* `--pending-deprecation`
2706-
* `--policy-integrity`
27072685
* `--preserve-symlinks-main`
27082686
* `--preserve-symlinks`
27092687
* `--prof-process`
@@ -3178,7 +3156,6 @@ node --stack-trace-limit=12 -p -e "Error.stackTraceLimit" # prints 12
31783156
[ScriptCoverage]: https://chromedevtools.github.io/devtools-protocol/tot/Profiler#type-ScriptCoverage
31793157
[ShadowRealm]: https://github.com/tc39/proposal-shadowrealm
31803158
[Source Map]: https://sourcemaps.info/spec.html
3181-
[Subresource Integrity]: https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity
31823159
[V8 JavaScript code coverage]: https://v8project.blogspot.com/2017/12/javascript-code-coverage.html
31833160
[V8 code cache]: https://v8.dev/blog/code-caching-for-devs
31843161
[`"type"`]: packages.md#type

doc/api/deprecations.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2306,7 +2306,7 @@ Type: Documentation-only (supports [`--pending-deprecation`][])
23062306
`process.binding()` is for use by Node.js internal code only.
23072307

23082308
While `process.binding()` has not reached End-of-Life status in general, it is
2309-
unavailable when [policies][] or the [permission model][] are enabled.
2309+
unavailable when the [permission model][] is enabled.
23102310

23112311
### DEP0112: `dgram` private APIs
23122312

@@ -3796,7 +3796,6 @@ is deprecated to better align with recommendations per [NIST SP 800-38D][].
37963796
[legacy URL API]: url.md#legacy-url-api
37973797
[legacy `urlObject`]: url.md#legacy-urlobject
37983798
[permission model]: permissions.md#permission-model
3799-
[policies]: permissions.md#policies
38003799
[static methods of `crypto.Certificate()`]: crypto.md#class-certificate
38013800
[subpath exports]: packages.md#subpath-exports
38023801
[subpath imports]: packages.md#subpath-imports

doc/api/errors.md

Lines changed: 0 additions & 63 deletions
Original file line numberDiff line numberDiff line change
@@ -2166,68 +2166,6 @@ added:
21662166
An ESM loader hook returned without calling `next()` and without explicitly
21672167
signaling a short circuit.
21682168

2169-
<a id="ERR_MANIFEST_ASSERT_INTEGRITY"></a>
2170-
2171-
### `ERR_MANIFEST_ASSERT_INTEGRITY`
2172-
2173-
An attempt was made to load a resource, but the resource did not match the
2174-
integrity defined by the policy manifest. See the documentation for [policy][]
2175-
manifests for more information.
2176-
2177-
<a id="ERR_MANIFEST_DEPENDENCY_MISSING"></a>
2178-
2179-
### `ERR_MANIFEST_DEPENDENCY_MISSING`
2180-
2181-
An attempt was made to load a resource, but the resource was not listed as a
2182-
dependency from the location that attempted to load it. See the documentation
2183-
for [policy][] manifests for more information.
2184-
2185-
<a id="ERR_MANIFEST_INTEGRITY_MISMATCH"></a>
2186-
2187-
### `ERR_MANIFEST_INTEGRITY_MISMATCH`
2188-
2189-
An attempt was made to load a policy manifest, but the manifest had multiple
2190-
entries for a resource which did not match each other. Update the manifest
2191-
entries to match in order to resolve this error. See the documentation for
2192-
[policy][] manifests for more information.
2193-
2194-
<a id="ERR_MANIFEST_INVALID_RESOURCE_FIELD"></a>
2195-
2196-
### `ERR_MANIFEST_INVALID_RESOURCE_FIELD`
2197-
2198-
A policy manifest resource had an invalid value for one of its fields. Update
2199-
the manifest entry to match in order to resolve this error. See the
2200-
documentation for [policy][] manifests for more information.
2201-
2202-
<a id="ERR_MANIFEST_INVALID_SPECIFIER"></a>
2203-
2204-
### `ERR_MANIFEST_INVALID_SPECIFIER`
2205-
2206-
A policy manifest resource had an invalid value for one of its dependency
2207-
mappings. Update the manifest entry to match to resolve this error. See the
2208-
documentation for [policy][] manifests for more information.
2209-
2210-
<a id="ERR_MANIFEST_PARSE_POLICY"></a>
2211-
2212-
### `ERR_MANIFEST_PARSE_POLICY`
2213-
2214-
An attempt was made to load a policy manifest, but the manifest was unable to
2215-
be parsed. See the documentation for [policy][] manifests for more information.
2216-
2217-
<a id="ERR_MANIFEST_TDZ"></a>
2218-
2219-
### `ERR_MANIFEST_TDZ`
2220-
2221-
An attempt was made to read from a policy manifest, but the manifest
2222-
initialization has not yet taken place. This is likely a bug in Node.js.
2223-
2224-
<a id="ERR_MANIFEST_UNKNOWN_ONERROR"></a>
2225-
2226-
### `ERR_MANIFEST_UNKNOWN_ONERROR`
2227-
2228-
A policy manifest was loaded, but had an unknown value for its "onerror"
2229-
behavior. See the documentation for [policy][] manifests for more information.
2230-
22312169
<a id="ERR_MEMORY_ALLOCATION_FAILED"></a>
22322170

22332171
### `ERR_MEMORY_ALLOCATION_FAILED`
@@ -3801,7 +3739,6 @@ The native call from `process.cpuUsage` could not be processed.
38013739
[domains]: domain.md
38023740
[event emitter-based]: events.md#class-eventemitter
38033741
[file descriptors]: https://en.wikipedia.org/wiki/File_descriptor
3804-
[policy]: permissions.md#policies
38053742
[relative URL]: https://url.spec.whatwg.org/#relative-url-string
38063743
[self-reference a package using its name]: packages.md#self-referencing-a-package-using-its-name
38073744
[special scheme]: https://url.spec.whatwg.org/#special-scheme

0 commit comments

Comments
 (0)