Node.js 14.0.0 (64-bit)

What's new in this version:

Deprecations:
- (SEMVER-MAJOR) crypto: move pbkdf2 without digest to EOL
- (SEMVER-MAJOR) fs: deprecate closing FileHandle on garbage collection
- (SEMVER-MAJOR) http: move OutboundMessage.prototype.flush to EOL
- (SEMVER-MAJOR) lib: move GLOBAL and root aliases to EOL
- (SEMVER-MAJOR) os: move tmpDir() to EOL
- (SEMVER-MAJOR) src: remove deprecated wasm type check
- (SEMVER-MAJOR) stream: move _writableState.buffer to EOL
- (SEMVER-MINOR) doc: deprecate process.mainModule
- (SEMVER-MINOR) doc: deprecate process.umask() with no arguments

ECMAScript Modules - Experimental Warning Removal:
- module: remove experimental modules warning
- In Node.js 13 we removed the need to include the --experimental-modules flag, but when running EcmaScript Modules in Node.js, this would still result in a warning ExperimentalWarning: The ESM module loader is experimental.
- As of Node.js 14 there is no longer this warning when using ESM in Node.js. However, the ESM implementation in Node.js remains experimental. As per our stability index: “The feature is not subject to Semantic Versioning rules. Non-backward compatible changes or removal may occur in any future release.” Users should be cautious when using the feature in production environments.
- Please keep in mind that the implementation of ESM in Node.js differs from the developer experience you might be familiar with. Most transpilation workflows support features such as optional file extensions or JSON modules that the Node.js ESM implementation does not support. It is highly likely that modules from transpiled environments will require a certain degree of refactoring to work in Node.js. It is worth mentioning that many of our design decisions were made with two primary goals. Spec compliance and Web Compatibility. It is our belief that the current implementation offers a future proof model to authoring ESM modules that paves the path to Universal JavaScript. Please read more in our documentation.
- The ESM implementation in Node.js is still experimental but we do believe that we are getting very close to being able to call ESM in Node.js “stable”. Removing the warning is a huge step in that direction.

ew V8 ArrayBuffer API:
- src: migrate to new V8 ArrayBuffer API
- Multiple ArrayBuffers pointing to the same base address are no longer allowed by V8. This may impact native addons

Toolchain and Compiler Upgrades:
- (SEMVER-MAJOR) build: update macos deployment target to 10.13 for 14.x
- (SEMVER-MAJOR) doc: update cross compiler machine for Linux armv7
- (SEMVER-MAJOR) doc: update Centos/RHEL releases use devtoolset-8
- (SEMVER-MAJOR) doc: remove SmartOS from official binaries
- (SEMVER-MAJOR) win: block running on EOL Windows versions
- It is expected that there will be an ABI mismatch on ARM between the Node.js binary and native addons. Native addons are only broken if they
- interact with std::shared_ptr. This is expected to be fixed in a later version of Node.js 14
- Update to V8 8.1
- (SEMVER-MAJOR) deps: update V8 to 8.1.307.20

Other Notable Changes:
- cli, report: move --report-on-fatalerror to stable
- deps: upgrade to libuv 1.37.0
- fs: add fs/promises alias module