Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

process: deprecate features.{ipv6,uv} and features.tls_* #55545

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions doc/api/deprecations.md
Original file line number Diff line number Diff line change
Expand Up @@ -3774,6 +3774,33 @@ Type: Runtime

The `util.getCallSite` API has been removed. Please use [`util.getCallSites()`][] instead.

### DEP0187: `process.features.ipv6` and `process.features.uv`

<!-- YAML
changes:
- version: REPLACEME
pr-url: /~https://github.com/nodejs/node/pull/55545
description: Documentation-only deprecation.
-->

Type: Documentation-only

These properties are unconditionally `true`. Any checks based on these properties are redundant.

### DEP0188: `process.features.tls_*`

<!-- YAML
changes:
- version: REPLACEME
pr-url: /~https://github.com/nodejs/node/pull/55545
description: Documentation-only deprecation.
-->

Type: Documentation-only

`process.features.tls_alpn`, `process.features.tls_ocsp`, and `process.features.tls_sni` are
deprecated, as their values are guaranteed to be identical to that of `process.features.tls`.

[NIST SP 800-38D]: https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-38d.pdf
[RFC 6066]: https://tools.ietf.org/html/rfc6066#section-3
[RFC 8247 Section 2.4]: https://www.rfc-editor.org/rfc/rfc8247#section-2.4
Expand Down
31 changes: 30 additions & 1 deletion doc/api/process.md
Original file line number Diff line number Diff line change
Expand Up @@ -1930,12 +1930,18 @@ A boolean value that is `true` if the current Node.js build includes the inspect

<!-- YAML
added: v0.5.3
deprecated: REPLACEME
-->

> Stability: 0 - Deprecated. This property is always true, and any checks based on it are
> redundant.

* {boolean}

A boolean value that is `true` if the current Node.js build includes support for IPv6.

Since all Node.js builds have IPv6 support, this value is always `true`.

## `process.features.require_module`

<!-- YAML
Expand Down Expand Up @@ -1963,32 +1969,50 @@ A boolean value that is `true` if the current Node.js build includes support for

<!-- YAML
added: v4.8.0
deprecated: REPLACEME
-->

> Stability: 0 - Deprecated. Use `process.features.tls` instead.

* {boolean}

A boolean value that is `true` if the current Node.js build includes support for ALPN in TLS.

In Node.js 11.0.0 and later versions, the OpenSSL dependencies feature unconditional ALPN support.
This value is therefore identical to that of `process.features.tls`.

## `process.features.tls_ocsp`

<!-- YAML
added: v0.11.13
deprecated: REPLACEME
-->

> Stability: 0 - Deprecated. Use `process.features.tls` instead.

* {boolean}

A boolean value that is `true` if the current Node.js build includes support for OCSP in TLS.

In Node.js 11.0.0 and later versions, the OpenSSL dependencies feature unconditional OCSP support.
This value is therefore identical to that of `process.features.tls`.

## `process.features.tls_sni`

<!-- YAML
added: v0.5.3
deprecated: REPLACEME
-->

> Stability: 0 - Deprecated. Use `process.features.tls` instead.

* {boolean}

A boolean value that is `true` if the current Node.js build includes support for SNI in TLS.

In Node.js 11.0.0 and later versions, the OpenSSL dependencies feature unconditional SNI support.
This value is therefore identical to that of `process.features.tls`.

## `process.features.typescript`

<!-- YAML
Expand All @@ -2008,12 +2032,17 @@ A value that is `"strip"` if Node.js is run with `--experimental-strip-types`,

<!-- YAML
added: v0.5.3
deprecated: REPLACEME
-->

> Stability: 0 - Deprecated. This property is always true, and any checks based on it are
> redundant.

* {boolean}

A boolean value that is `true` if the current Node.js build includes support for libuv.
Since it's currently not possible to build Node.js without libuv, this value is always `true`.

Since it's not possible to build Node.js without libuv, this value is always `true`.

## `process.finalization.register(ref, callback)`

Expand Down
Loading