From 743015422a1c70966fca1614c38db9a7665de31f Mon Sep 17 00:00:00 2001 From: stdlib-bot <82920195+stdlib-bot@users.noreply.github.com> Date: Wed, 10 Sep 2025 02:27:02 +0000 Subject: [PATCH] docs: update related packages sections --- lib/node_modules/@stdlib/net/http-server/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/node_modules/@stdlib/net/http-server/README.md b/lib/node_modules/@stdlib/net/http-server/README.md index f4741d89227e..225c8dc839c8 100644 --- a/lib/node_modules/@stdlib/net/http-server/README.md +++ b/lib/node_modules/@stdlib/net/http-server/README.md @@ -114,7 +114,7 @@ The function supports the following parameters: ## Notes -- Which server options are supported depends on the Node.js version. Older Node.js versions (e.g., <= v8.12.0) do not support an options object when calling [`http.createServer`][nodejs-http-create-server], and, for those versions, any options supported by [`http.createServer`][nodejs-http-create-server] in later Node.js versions are ignored. +- Which server options are supported depends on the Node.js version. Older Node.js versions (e.g., <= v8.12.0) do not support an options object when calling [`http.createServer`][nodejs-http-create-server], and, for those versions, any options supported by [`http.createServer`][nodejs-http-create-server] in later Node.js versions are ignored. - Port hunting can be useful in a microservice deployment. When a `port` is randomly assigned (`options.port=0`), if a server fails and is restarted, the server is unlikely to bind to its previous `port`. By allowing a constrained search, assuming no lower `ports` within a specified range have freed up in the meantime, the likelihood of listening on the same `port` is increased. A server can typically restart and bind to the same `port` faster than binding to a new `port` and re-registering with a microservice registry, thus minimizing possible service interruption and downtime.