Philipp Partosch 46a936d7de added all files to project | 2 years ago | |
---|---|---|
.. | ||
index.d.ts | 2 years ago | |
index.js | 2 years ago | |
license | 2 years ago | |
package.json | 2 years ago | |
readme.md | 2 years ago |
Get an available TCP port
$ npm install get-port
const getPort = require('get-port');
(async () => {
console.log(await getPort());
//=> 51402
})();
Pass in a preferred port:
(async () => {
console.log(await getPort({port: 3000}));
// Will use 3000 if available, otherwise fall back to a random port
})();
Pass in an array of preferred ports:
(async () => {
console.log(await getPort({port: [3000, 3001, 3002]}));
// Will use any element in the preferred ports array if available, otherwise fall back to a random port
})();
Use the makeRange()
helper in case you need a port in a certain range:
(async () => {
console.log(await getPort({port: getPort.makeRange(3000, 3100)}));
// Will use any port from 3000 to 3100, otherwise fall back to a random port
})();
Returns a Promise
for a port number.
Type: object
Type: number | Iterable<number>
A preferred port or an iterable of preferred ports to use.
Type: string
The host on which port resolution should be performed. Can be either an IPv4 or IPv6 address.
Make a range of ports from
…to
.
Returns an Iterable
for ports in the given range.
Type: number
First port of the range. Must be in the range 1024
…65535
.
Type: number
Last port of the range. Must be in the range 1024
…65535
and must be greater than from
.
There is a very tiny chance of a race condition if another process starts using the same port number as you in between the time you get the port number and you actually start using it.
Race conditions in the same process are mitigated against by using a lightweight locking mechanism where a port will be held for a minimum of 15 seconds and a maximum of 30 seconds before being released again.