Italian Translation Report: Node.js [Part 45 - 1365 words]

Deprecated APIs
Node.js may deprecate APIs when either: use of the API is considered to be unsafe, an improved alternative API has been made available, or breaking changes to the API are expected in a future major release.
Node.js utilizes three kinds of Deprecations:
Documentation-only
Runtime
End-of-Life
A Documentation-only deprecation is one that is expressed only within the Node.js API docs.
These generate no side-effects while running Node.js. Some Documentation-only deprecations trigger a runtime warning when launched with flag (or its alternative, environment variable), similarly to Runtime deprecations below.
Documentation-only deprecations that support that flag are explicitly labeled as such in the list of Deprecated APIs
A Runtime deprecation will, by default, generate a process warning that will be printed to the first time the deprecated API is used.
When the command-line flag is used, a Runtime deprecation will cause an error to be thrown.
An End-of-Life deprecation is used to identify code that either has been removed or will soon be removed from Node.js.
Revoking deprecations
Occasionally, the deprecation of an API may be reversed.
In such situations, this document will be updated with information relevant to the decision.
However, the deprecation identifier will not be modified.
List of Deprecated APIs
The method is deprecated.
Use instead
Please use a userland alternative.
The property is deprecated.
The property is deprecated and should not be used.
The function and constructor are deprecated due to API usability issues that can potentially lead to accidental security issues.
As an alternative, use of the following methods of constructing objects is strongly recommended:
Create a with initialized memory.
Create a with a copy of
Create a that wraps the given
Create a that copies
As of v10.0.0, a deprecation warning is printed at runtime when is used or when the calling code is
outside in order to better target developers, rather than users.
Within the module's and methods, the option is deprecated.
In an earlier version of the Node.js, a boolean property with the name was added to the object.
The intent of this property was to provide an indication of how and why the instance exited.
In Node.js 6.0.0, the old property was deprecated and replaced with a new property.
The old property name did not precisely describe the actual semantics and was unnecessarily emotion-laden.
When requiring access to constants relevant to specific Node.js builtin modules, developers should instead refer to the property exposed by the relevant module.
For instance, and
Use of the API without specifying a digest was deprecated in Node.js 6.0 because the method defaulted to using the non-recommended digest.
Previously, a deprecation warning was printed.
Starting in Node.js 8.0.0, calling or with an undefined will throw a
has been removed.
Recover from failed I/O actions explicitly via error event handlers set on the domain instead.
asynchronous function without callback
Calling an asynchronous function without a callback throws a in Node.js 10.0.0 onwards.
The legacy interface is deprecated.
Use the API as mentioned in the documentation instead.
The and aliases for the property have been deprecated and should no longer be used.
was a non-standard extension and has been removed.
Unhandled promise rejections are deprecated.
In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
In certain cases, may resolve outside the package directory.
This behavior is deprecated and will be removed in a future major Node.js release.
The method is now deprecated as its inclusion in the API is not useful.
The environment variable was removed.
activates the legacy V8 debugger interface, which has been removed as of V8 5.8. It is replaced by Inspector which is activated with instead.
The method was never documented as an officially supported API.
The API was deprecated in documentation in Node.js 0.11.3. Users should use instead.
The module's constant, used for option, has been removed.
Its behavior has been functionally identical to that of since Node.js 6.0.0, when V8 5.0 was imported.
The environment variable is used to set the underlying of an interactive session.
Its value, is also removed.
Please instead use one of the public methods for working with outgoing headers.
The and properties were never documented as officially supported properties.
corresponds to the legacy CLI debugger which has been replaced with a V8-inspector based CLI debugger available through
has been removed in V8 and is not available in Node.js
was an experimental API.
was renamed to for clarity.
This change was made while was an experimental API.
Accessing several internal, undocumented properties of instances with inappropriate names has been deprecated.
As the original API was undocumented and not generally useful for non-internal code, no replacement API is provided.
was removed from userland visibility.
is a trivial parsing helper that was made public by mistake. This function can usually be replaced with:
This function is not completely equivalent to
One difference is that does url decoding:
Using a property named on an object to specify a custom inspection function for is deprecated.
For backward compatibility with Node.js prior to version 6.4.0, both may be specified.
The internal was not intended for public use.
However, userland modules have found it useful.
The internal API has been deprecated and replaced with an identical, public method.
usage with a file descriptor has been deprecated.
Please use or to work with file descriptors.
is only necessary for the internal mechanics of the itself. Do not use this function.
The option to and could be set to to disable ECDH entirely on the server only
This mode is deprecated in preparation for migrating to OpenSSL 1.1.0 and consistency with the client.
Use the parameter instead.
requiring bundled internal dependencies
Since Node.js versions 4.4.0 and 5.2.0, several modules only intended for internal usage are mistakenly exposed to user code through
These modules are:
The modules do not have any exports, and if not imported in a specific order would in fact throw errors.
As such there are virtually no legitimate usecases for importing them through
On the other hand, may be installed locally through a package manager, as it is published on the npm registry under the same name.
No source code modification is necessary if that is done.
doesn't emit the or event and can thus cause a lot of issues.
Importing assert directly is not recommended as the exposed functions will use loose equality checks.
The API is the same as the legacy assert but it will always use strict equality checks.
Node.js supports all GCM authentication tag lengths which are accepted by OpenSSL when calling
This behavior will change in a future version at which point only authentication tag lengths of and bits will be allowed.
Authentication tags whose length is not included in this list will be considered invalid in compliance with
Users of that add the property to carry context, should start using the variant of or or the high-level class.
The embedded API provided by AsyncHooks exposes and methods which are very easy to use incorrectly which can lead to unrecoverable errors.
Use API instead which provides a much safer, and more convenient, alternative.
All input is going to be verified, no matter if it is set to true or not. Skipping the verification could lead to hard to find errors and crashes.
When assigning a non-string property to, the assigned value is implicitly converted to a string.
This behavior is deprecated if the assigned value is not a string, boolean, or number.
In the future, such assignment may result in a thrown error.
Please convert the property to a string before assigning it to
Using and should be avoided as they use a weak key derivation function (MD5 with no salt) and static initialization vectors.
It is recommended to derive a key using and to use and to obtain the and objects respectively.
This was an undocumented helper function not intended for use outside Node.js core and obsoleted by the removal of NPN (Next Protocol Negotiation) support.
This original name was chosen because it also made sense to interpret the value as the number of bytes read by the engine, but is inconsistent with other streams in Node.js that expose values under these names.