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

port-type

v0.2.1

Published

Categorize port numbers by semantics.

Downloads

12

Readme

port-type Build status for port-type on Circle CI.

Categorize port numbers by semantics.

Why?

  • Helps you screen user input.
  • Identify port ranges by name.
  • Can tell you if it is possible to start a server.

Install

npm install port-type --save

Usage

Get it into your program.

const portType = require('port-type');

Identify the type of port you are working with, as a lowercase string.

portType.is(123);  // => "system"

But why type all that and still have to do a strict equality check? Fuggedaboutit.

portType.isSystem(123);  // => true

There are other types, too.

const port = 4444;
portType.isSystem(port);      // => false
portType.isRegistered(port);  // => true
portType.isDynamic(port);     // => false

Still wondering what these are exactly? They are simple number ranges, which determine how different sets of ports should be used. You can get the definition of each range, too.

portType.range.system.min;      // => 1
portType.range.registered.max;  // => 49151

Eventually you will want to determine if it is even remotely possible or sensible to try to listen on a port.

const port = 80;
portType.needsRoot(port);   // => false on Windows, true everywhere else
portType.haveRights(port);  // => true on Windows, false everywhere else unless running as root

Isn't that warm and cozy? Just look at it.

Contributing

See our contributing guidelines for more details.

  1. Fork it.
  2. Make a feature branch: git checkout -b my-new-feature
  3. Commit your changes: git commit -am 'Add some feature'
  4. Push to the branch: git push origin my-new-feature
  5. Submit a pull request.

License

MPL-2.0 © Seth Holladay

Go make something, dang it.