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

compromise-numbers

v1.4.0

Published

plugin for nlp-compromise

Downloads

10,442

Readme

const nlp = require('compromise')
nlp.extend(require('compromise-numbers'))

let doc = nlp('I’d like to request seventeen dollars for a push broom rebristling')
doc.numbers().debug()
// 17

Demo

API

Opinions:

if a number is changed within a sentence, attempts are made at sentence-agreement - in both a leading determiner, and the plurality of a following noun. This is done safely, but it may have sneaky or unintended effects for some applications.

money, fractions, and percentages will be returned and work fine in .numbers(), but can be isolated with .money(), .fractions() and .percentages()

Fractions

.fractions() will parse things like '1/3', 'one out of three', and 'one third'.

it will not pluck the fraction from the end of a number, like 'six and one third'. 'one third' will still have a #Fraction tag.

Things can get pretty crazy - and there are some human-ambiguous fractions like 'five hundred thousandths'. In these cases it tries its best.

Attempts are also made to avoid conversational fractions, like 'half time show' or dates like '3rd quarter 2020'.

Money

  • ambiguous currencies: many currency symbols are re-used, for different countries. We try to make some safe assumptions about this. compromise-numbers assumes a naked $ is USD, £ is GBP, is South Korean, and 'kr' is Swedish Krona.

Configuring this should be possible in future versions.

  • decimal currencies: nlp('five cents').money().get(0) will return 0.05 (like it should), but .numbers().get() will return 5. This is a tricky thing that we should solve, somehow.

Years and Time

times like 5pm are parsed and handled by compromise-dates and are not returned by .numbers().

particularly, #Year tags are applied to numbers in a delicate way.

Decimal seperators

compromise-numbers uses the period decimal point and supports comma as a thousands-seperator. Some european or latin-american number formats like comma-decimals, or space-separated-thousands do not parse properly.

Serial numbers

attempts are made to ignore phone-numbers, postal-codes and credit-card numbers from .numbers() results, but there may be numbers used in other ways that are not accounted for.

work in progress!

MIT