Auto-generated commit

Author: stdlib-bot

CHANGELOG.md

@@ -22,6 +22,7 @@
 
 <details>
 
+-   [`6bb94b5`](https://github.com/stdlib-js/stdlib/commit/6bb94b5e2b1b81704a18e8b8ba6ed2bcccce4c23) - **docs:** add note _(by Athan Reines)_
 -   [`9f3732f`](https://github.com/stdlib-js/stdlib/commit/9f3732f2587d7e0f4ad16589ca5900b0cf20bbc0) - **docs:** fix examples _(by Athan Reines)_
 -   [`1f08a8b`](https://github.com/stdlib-js/stdlib/commit/1f08a8b3c6f9c39c316380b1c059ddac187d004c) - **docs:** fix examples _(by Athan Reines)_
 -   [`4eb8f54`](https://github.com/stdlib-js/stdlib/commit/4eb8f54376072921b0c76058dd239341a205acbc) - **test:** fix option name _(by Athan Reines)_

README.md

@@ -178,6 +178,7 @@ The function supports the following parameters:
 
 ## Notes
 
+-   The function requires that either the `pfx` option is provided or a `cert`/`key` option pair is provided.
 -   Which server options are supported depends on the Node.js version.
 -   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.