port-authority

Utilities for dealing with ports in Node apps

by Rich-Harris

Star on GitHub Forknpm

JavaScript

57 stars 7 forks 6 contributorsQuiet · 3y agoSince 2018

Meet the team

See all 6 on GitHub →

Rich-Harris41 contributions

Conduitry3 contributions

sidharthv963 contributions

bryanwood3 contributions

EmilTholin1 contribution

Languages

View on GitHub →

JavaScript100%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

2 of 6 standards met

Community profile →

✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template

Recent fixes

View closed PRs →

ModerniseMergedPR

Converts the codebase to native JavaScript modules, and generally tidies things up a bit. The and methods are replaced with and

Rich-Harris · 4y ago

Bind server to localhostMergedPR

Fixes #8 and https://github.com/sveltejs/kit/issues/1591

sidharthv96 · 4y ago

Allow checking a specific hostClosedIssue

Currently, the port checking behavior relies on the default behavior of , which is to bind to the [unspecified IPv6 or IPv4 address][1]. Some applications, such as Chrome's remote debugging, bind to a different address, such as only , meaning won't detect that port as already in use. This causes this check in [Sapper][2]: https://github.com/sveltejs/sapper/blob/e0de230e1391ec1b4a404faea57fd2cc8bbf9812/src/api/dev.ts#L158-L159 to incorrectly declare that port 9222 is not in use if it is in use by another node.js or Chrome process. [1]: https://nodejs.org/api/net.html#net_server_listen_port_host_backlog_callback [2]: https://github.com/sveltejs/sapper

jarrodldavis · 4y ago

Structured data for AI agents

Repository: Rich-Harris/port-authority. Description: Utilities for dealing with ports in Node apps Stars: 57, Forks: 7. Primary language: JavaScript. Languages: JavaScript (100%). Open PRs: 2, open issues: 2. Last activity: 3y ago. Community health: 42%. Top contributors: Rich-Harris, Conduitry, sidharthv96, bryanwood, EmilTholin.