wait-port
npmv1.1.0Utility to wait for a TCP port to open.
Adopt with care
wait-port is usable, with caveats. Last published 1085 days ago.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- DMaintenance: grade D, Poor — a real concern.
Last published 1085 days ago.
- AWeight: grade A, Excellent.
Pulls in 4 transitive packages, about 292 KB installed (at least — some of the tree is still being crawled).
- 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 wait-port 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.
Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.
Licenses in the dependency tree
Every license you inherit by installing wait-port, not just its own. Check this before a legal review, not after.
Compatibility
- Node.js
- node >=10
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the wait-port README.
const waitPort = require('wait-port');
const params = {
host: 'google.com',
port: 443,
};
waitPort(params)
.then(({ open, ipVersion }) => {
if (open) console.log(`The port is now open on IPv${ipVersion}!`);
else console.log('The port did not open before the timeout...');
})
.catch((err) => {
console.err(`An unknown error occured while waiting for the port: ${err}`);Dependencies
Declared by wait-port v1.1.0. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (3)
Dev (8)
Used by
Popular packages that depend on wait-port.
Relationship graph
Dependencies (left) and dependents (right) of wait-port.
Frequently installed together
Convert a camelized string into a lowercased one with a custom separator: unicornRainbow → unicorn_rainbow
A helper utility for logging of WebdriverIO packages
Mozilla's Geckodriver for Node.js
Get an available port
An NPM wrapper for handling the Safaridriver binary.
split a Text Stream into a Line Stream, using Stream 3
Resolve things like Node.js — ponyfill for `import.meta.resolve`
Utility package providing type information for a variety of WebdriverIO interfaces
Download and launch browsers
Microsofts' EdgeDriver for Node.js
Find apps installed on your system. This util will help to find executables of a known app like Chrome, Firefox,... on Windows, Linux, and macOS out of the box.
An HTTP(s) proxy `http.Agent` implementation for HTTPS
Release history
No releases in the last two years, typically about 11 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.1.0latest | 3 years ago | 41 KB | MIT |
| 1.0.4 | 3 years ago | 41 KB | MIT |
| 1.0.3 | 3 years ago | 41 KB | MIT |
| 1.0.1 | 4 years ago | 45 KB | MIT |
| 1.0.0 | 4 years ago | 40 KB | MIT |
| 0.3.1 | 4 years ago | 42 KB | MIT |
| 0.3.0 | 4 years ago | 42 KB | MIT |
| 0.2.14 | 4 years ago | 41 KB | MIT |
| 0.2.13 | 4 years ago | 41 KB | MIT |
| 0.2.9 | 6 years ago | 180 KB | MIT |
| 0.2.8 | 6 years ago | 180 KB | MIT |
| 0.2.7 | 6 years ago | 180 KB | MIT |
| 0.2.6 | 7 years ago | 180 KB | MIT |
| 0.2.4 | 7 years ago | 189 KB | MIT |
| 0.2.3 | 7 years ago | 186 KB | MIT |
Overview
wait-port is an npm package that utility to wait for a TCP port to open. It has 3 known dependents in the graph. The latest version is 1.1.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need utility to wait for a TCP port to open and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use wait-port?
wait-port is usable, with caveats. Last published 1085 days ago.
How do I install wait-port?
Run `npm install wait-port` to add wait-port to your npm project.
How many dependencies does wait-port have?
wait-port declares 11 direct dependencies and pulls in 4 packages in total once its runtime tree is resolved totalling about 292 KB on disk.
What license is wait-port released under?
wait-port is distributed under the MIT license.
How popular is wait-port?
npm does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on wait-port.
Is wait-port still maintained?
The most recent release of wait-port (v1.1.0) was published 3 years ago.
Does wait-port run install scripts?
No. wait-port does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.