npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

devonport

v1.0.0

Published

Generate TCP ports from strings, for predictable local development

Downloads

12

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:

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)