# devonport

> Generate TCP ports from strings, for predictable local development

Latest version **1.0.0** (published 2016-08-17) · ISC license · 0 weekly downloads

## Install

```sh
npm install devonport
pnpm add devonport
yarn add devonport
bun add devonport
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.0.0 |
| Published | 2016-08-17 |
| First published | 2016-08-17 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | g5095 |
| Maintainers | g5095 |
| Keywords | port, tcp, local-dev, ponies, jazz |

## Links

- npm: https://www.npmjs.com/package/devonport
- Repository: https://github.com/g5095/devonport
- Homepage: https://github.com/g5095/devonport#readme
- Issues: https://github.com/g5095/devonport/issues
- npm.io page: https://npm.io/package/devonport

## Alternatives

- [@clerk/clerk-expo](https://npm.io/package/@clerk/clerk-expo.md) — 133.6K weekly downloads
- [@pothos/plugin-authz](https://npm.io/package/@pothos/plugin-authz.md) — 12.4K weekly downloads
- [@bounded-sh/client](https://npm.io/package/@bounded-sh/client.md) — 3.2K weekly downloads
- [@oxyhq/services](https://npm.io/package/@oxyhq/services.md) — 2.3K weekly downloads
- [@luigi-project/plugin-auth-oauth2](https://npm.io/package/@luigi-project/plugin-auth-oauth2.md) — 2.3K weekly downloads

## Recent versions

- 1.0.0 (latest) — 2016-08-17

## README

# Dev-On-Port

Generate TCP ports from strings, for predictable local development

### Purpose

Ever worked in a big dev team doing micro-services? Production deployment
is managed via a proper orchestration system but local dev can be a mess
when everyone's services are fighting for port 8000-8010. 

You need a predictable way of binding to a _probably_ unused port in
a predictable manner, so that other services can talk back to you reliably
in your local environment.

Enter Dev-On-Port! the handy-dandy device that turns your service name
into a port number between 1024 and 65000. 

### Example:

```javascript
const devonport = require('devonport');

let port = devonport('my-cool-service-name');  // 61410
```

Now use _port_ to bind too, and _port_ from client code to talk to your
local service by it's service name and not a number, it's like DNS for
your ports! (not really)

---
_Source: https://npm.io/package/devonport · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._