Security News
vlt Debuts New JavaScript Package Manager and Serverless Registry at NodeConf EU
vlt introduced its new package manager and a serverless registry this week, innovating in a space where npm has stagnated.
get-port-please
Advanced tools
The `get-port-please` npm package is designed to help developers find an available port on the host machine. It is particularly useful in scenarios where an application needs to start a server but must avoid port conflicts with other applications. This package offers flexibility in selecting ports, including the ability to specify preferred port ranges or fallback to any available port if the preferred ones are occupied.
Getting an available port
This feature allows you to get an available port on the machine. If no arguments are passed, it returns any available port.
const getPort = require('get-port-please');
getPort().then(port => {
console.log(`Available port: ${port}`);
});
Specifying preferred ports
This feature enables specifying an array of preferred ports. The function will return the first available port from the specified list or any available port if none from the list are free.
const getPort = require('get-port-please');
getPort({ preferredPorts: [3000, 3001, 3002] }).then(port => {
console.log(`Available port: ${port}`);
});
Specifying port ranges
This feature allows specifying ranges of ports to check for availability. It's useful when you need a port within a specific range.
const getPort = require('get-port-please');
getPort({ portRanges: [{ from: 8000, to: 8005 }] }).then(port => {
console.log(`Available port within range: ${port}`);
});
Similar to `get-port-please`, `portfinder` provides a way to get an available port on the host machine. However, `portfinder` focuses more on finding an open port by incrementing from a base port, rather than specifying preferred ports or ranges.
The `get-port` package also helps in finding an available port. While it shares similar basic functionality with `get-port-please`, it does not offer the same level of control over specifying port ranges or preferred port lists.
Get an available TCP port to listen
Install package:
yarn add get-port-please
# or
or npm install get-port-please
const { getPort } = require('get-port-please')
// or
import { getPort } from 'get-port-please'
function getPort(options?: GetPortOptions): Promise<number>
Try sequence is: port > ports > memo > random
interface GetPortOptions {
name?: string
random?: boolean
port?: number
ports?: number[]
memoDir?: string
memoName?: string
}
name
Unique name for port memorizing. Default is default
.
random
If enabled, port
and ports
will be ignored. Default is false
.
port
First port to check. Default is process.env.PORT || 3000
ports
Alternative ports to check. Default is [4000, 5000, 6000, 7000]
memoDir
/ memoName
Options passed to fs-memo
node_modules/get-port/dist
.get-port
MIT
FAQs
Get an available TCP port to listen
The npm package get-port-please receives a total of 753,751 weekly downloads. As such, get-port-please popularity was classified as popular.
We found that get-port-please demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt introduced its new package manager and a serverless registry this week, innovating in a space where npm has stagnated.
Security News
Research
The Socket Research Team uncovered a malicious Python package typosquatting the popular 'fabric' SSH library, silently exfiltrating AWS credentials from unsuspecting developers.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.