2022-07-13, Version 18.6.0 (Current)

Notable changes:

- esm: add chaining to loaders

PR-URL: #43789

CHANGELOG.md

@@ -35,7 +35,8 @@ release.
 </tr>
 <tr>
   <td valign="top">
-<b><a href="doc/changelogs/CHANGELOG_V18.md#18.5.0">18.5.0</a></b><br/>
+<b><a href="doc/changelogs/CHANGELOG_V18.md#18.6.0">18.6.0</a></b><br/>
+<a href="doc/changelogs/CHANGELOG_V18.md#18.5.0">18.5.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V18.md#18.4.0">18.4.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V18.md#18.3.0">18.3.0</a><br/>
 <a href="doc/changelogs/CHANGELOG_V18.md#18.2.0">18.2.0</a><br/>

doc/api/errors.md

@@ -2104,7 +2104,7 @@ for more information.
 ### `ERR_LOADER_CHAIN_INCOMPLETE`
 
 <!-- YAML
-added: REPLACEME
+added: v18.6.0
 -->
 
 An ESM loader hook returned without calling `next()` and without explicitly

doc/api/esm.md

@@ -8,7 +8,7 @@
 added: v8.5.0
 changes:
   - version:
-    - REPLACEME
+    - v18.6.0
     pr-url: https://github.com/nodejs/node/pull/42623
     description: Add support for chaining loaders.
   - version:
@@ -681,7 +681,7 @@ of Node.js applications.
 added: v8.8.0
 changes:
   - version:
-    - REPLACEME
+    - v18.6.0
     pr-url: https://github.com/nodejs/node/pull/42623
     description: Add support for chaining loaders.
   - version: v16.12.0
@@ -731,7 +731,7 @@ prevent unintentional breaks in the chain.
 
 <!-- YAML
 changes:
-  - version: REPLACEME
+  - version: v18.6.0
     pr-url: https://github.com/nodejs/node/pull/42623
     description: Add support for chaining resolve hooks. Each hook must either
       call `nextResolve()` or include a `shortCircuit` property set to `true`
@@ -823,7 +823,7 @@ export async function resolve(specifier, context, nextResolve) {
 
 <!-- YAML
 changes:
-  - version: REPLACEME
+  - version: v18.6.0
     pr-url: https://github.com/nodejs/node/pull/42623
     description: Add support for chaining load hooks. Each hook must either
       call `nextLoad()` or include a `shortCircuit` property set to `true` in
@@ -921,7 +921,7 @@ source to a supported one (see [Examples](#examples) below).
 
 <!-- YAML
 changes:
-  - version: REPLACEME
+  - version: v18.6.0
     pr-url: https://github.com/nodejs/node/pull/42623
     description: Add support for chaining globalPreload hooks.
 -->

doc/api/module.md

@@ -65,7 +65,7 @@ const siblingModule = require('./sibling-module');
 ### `module.isBuiltin(moduleName)`
 
 <!-- YAML
-added: REPLACEME
+added: v18.6.0
 -->
 
 * `moduleName` {string} name of the module

doc/api/net.md

@@ -284,7 +284,7 @@ Emitted when the server has been bound after calling [`server.listen()`][].
 ### Event: `'drop'`
 
 <!-- YAML
-added: REPLACEME
+added: v18.6.0
 -->
 
 When the number of connections reaches the threshold of `server.maxConnections`,

doc/api/v8.md

@@ -879,7 +879,7 @@ occur synchronously in the case of `Promise.resolve()` or `Promise.reject()`.
 ## Startup Snapshot API
 
 <!-- YAML
-added: REPLACEME
+added: v18.6.0
 -->
 
 > Stability: 1 - Experimental
@@ -950,7 +950,7 @@ snapshot cannot use these APIs again.
 ### `v8.startupSnapshot.addSerializeCallback(callback[, data])`
 
 <!-- YAML
-added: REPLACEME
+added: v18.6.0
 -->
 
 * `callback` {Function} Callback to be invoked before serialization.
@@ -965,7 +965,7 @@ into a form more suitable for serialization.
 ### `v8.startupSnapshot.addDeserializeCallback(callback[, data])`
 
 <!-- YAML
-added: REPLACEME
+added: v18.6.0
 -->
 
 * `callback` {Function} Callback to be invoked after the snapshot is
@@ -982,7 +982,7 @@ when the application is restarted from the snapshot.
 ### `v8.startupSnapshot.setDeserializeMainFunction(callback[, data])`
 
 <!-- YAML
-added: REPLACEME
+added: v18.6.0
 -->
 
 * `callback` {Function} Callback to be invoked as the entry point after the
@@ -1000,7 +1000,7 @@ needs to be provided to the deserialized application.
 ### `v8.startupSnapshot.isBuildingSnapshot()`
 
 <!-- YAML
-added: REPLACEME
+added: v18.6.0
 -->
 
 * Returns: {boolean}