get-port-please
npmv3.2.0TypeScriptGet an available TCP port to listen
Adopt with care
get-port-please is usable, with caveats. Last published 377 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- CMaintenance: grade C, Fair — worth a look.
Last published 377 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 28 KB installed.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- ALicense: grade A, Excellent.
MIT — permissive, with no copyleft found in the dependency tree.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding get-port-please to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- No constraint declared
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
Quick start
A usage example from the get-port-please README.
// ESM
import {
getPort,
checkPort,
getRandomPort,
waitForPort,
getSocketAddress,
isSocketSupported,
cleanSocket
} from "get-port-please";
// CommonJS
const {
getPort,Dependencies
Declared by get-port-please v3.2.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (10)
Used by
Popular packages that depend on get-port-please.
Framework for building generic devframes
Portable, hub-native terminal panel for devframe — readonly output streaming and fully interactive PTY shells (TUI-capable).
Devframe plugin — the hub message feed as a portable panel: browse, filter, and dismiss `ctx.messages` entries from any hub host.
Cross-platform WebSocket Servers for Node.js, Deno, Bun and Cloudflare Workers
Universal Server.
Minimal H(TTP) framework built for high performance and portability.
DevTools for Vitest
Devframe plugin — a self-inspector for the RPC registry, shared state, and agent surface of a devframe connection.
Relationship graph
Dependencies (left) and dependents (right) of get-port-please.
Frequently installed together
Next generation testing framework powered by Vite
Native-ESM powered web dev build tool
Framework for building generic devframes
Structured diagnostic code library
Simple yet powerful framework for building command-line apps.
Minimal H(TTP) framework built for high performance and portability.
TypeScript definitions for node
Let’s get serious about color
Framework-neutral hub layer for devframe — docks, terminals, messages, commands.
V8 coverage provider for Vitest
Model Context Protocol implementation for TypeScript
A fast and minimal alternative to globby and fast-glob
Release history
1 release in the last two years, typically about 18 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 3.2.0latest | 1 year ago | 28 KB | MIT |
| 3.1.2 | 2 years ago | 24 KB | MIT |
| 3.1.1 | 2 years ago | 30 KB | MIT |
| 3.1.0 | 2 years ago | 30 KB | MIT |
| 3.0.3 | 2 years ago | 29 KB | MIT |
| 3.0.2 | 2 years ago | 26 KB | MIT |
| 3.0.1 | 3 years ago | 14 KB | MIT |
| 2.6.1 | 4 years ago | 15 KB | MIT |
| 2.6.0 | 4 years ago | 15 KB | MIT |
| 2.5.0 | 4 years ago | 15 KB | MIT |
| 2.4.3 | 4 years ago | 10 KB | MIT |
| 2.4.2 | 4 years ago | 10 KB | MIT |
| 2.4.1 | 4 years ago | 10 KB | MIT |
| 2.4.0 | 4 years ago | 10 KB | MIT |
| 2.3.0 | 4 years ago | 7.4 KB | MIT |
Overview
get-port-please is an npm package that get an available TCP port to listen. It has 8 known dependents in the graph. The latest version is 3.2.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need get an available TCP port to listen and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use get-port-please?
get-port-please is usable, with caveats. Last published 377 days ago.
How do I install get-port-please?
Run `npm install get-port-please` to add get-port-please to your npm project.
What license is get-port-please released under?
get-port-please is distributed under the MIT license.
How popular is get-port-please?
npm does not publish download counts. Within PackageGraph's crawl, 8 known packages depend on get-port-please.
Is get-port-please still maintained?
The most recent release of get-port-please (v3.2.0) was published 1 year ago.
Does get-port-please run install scripts?
No. get-port-please does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.