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

nanpa_tools

v0.0.1

Published

A library with tools to work with NANPA numbers

Downloads

4

Readme

License npm version js-standard-style

Build Status Coverage Status Code Climate Issue Count

nanpa_tools

This library is used to handle NANPA telephone numbers while at the same time gathering information about them.

Installing

Add this library to your package.json configuration:

  "dependencies": {
    "nanpa_tools": "latest"
  }

Using it

Below you will find a few examples for the most common usage. More examples can be found in the tests.

Import the module in your code

  var nanpa_tools = require('nanpa_tools');

Figuring out if a given number is a NANPA number.

  if (nanpa_tools.isNanpa("13055556666")) {
    ...
  }
}

Getting information for a NANPA number

  var result = nanpa_tools.resolve("13055556666");

If the number is a NANPA number, the result object will contain:

  • npa: Area code.
  • nxx: Exchange code.
  • num: Subscriber number.
  • countryCode: ISO2 code for the country.
  • countryName: Full country name (in English).
  • usStateCode: Only present for US numbers. 2-letter state code.
  • usStateName: Only present for US numbers. Full state name.
  • caProvinceCode: Only present for Canada numbers. 2-letter province code.
  • caProvinceName: Only present for Canada numbers. Full province name.
  • isTollFree: true if the given number is a Toll Free.
  • isPremium: true if the given number is a Premium Number.

Detecting Intra- or Inter-State calls

  var result = nanpa_tools.resolveInterIntra("13055556666", "17866667777");

The result object will contain:

  • number1: A result object like the one described above.
  • number2: A result object like the one described above.
  • isIntra: true if the call should be considered Intra-State. US calls only.
  • isInter: true if the call should be considered Inter-State. US calls only.

Developers

This project uses standard npm scripts. Current tasks include:

  • test: Runs Mocha tests.
  • jsdoc: Runs JSDoc3.
  • eslint: Runs ESLint.
  • coverage: Runs the tests and then Instanbul to get a coverage report.
  • build: This is the default task, and will run all the other tasks.

Running an npm task

To run a task, just do:

npm run build

Contributing

To contribute:

  • Make sure you open a concise and short pull request.
  • Throw in any needed unit tests to accomodate the new code or the changes involved.
  • Run npm run build and make sure everything is ok before submitting the pull request (make eslint happy).
  • Your code must comply with the Javascript Standard Style, ESLint should take care of that.

License

The source code is released under Apache 2 License.

Check LICENSE file for more information.