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

multi-number-parse

v1.1.0

Published

Library for parsing numbers in any valid format.

Downloads

1,451

Readme

Multi-Number Parse (multi-number-parse)

npm package

Build status

Library for parsing numbers in any valid format.

This library was motivated by the need to support a wide range of number formats from users. Users sometime paste prices, percentages and whatnot from spreadsheets or websites, and we couldn't force them to always use either the international format ("12345.67") or the specific user locale.

Install

npm install multi-number-parse --save-prod

Usage

This library always returns a number, even if that number is Number.NaN. Usage is very simple:

import parse from 'multi-number-parse';

parse('2,543.56'); // returns 2543.56
parse('10 654.1234'); // returns 10654.1234
parse('2.654$10'); // returns 2654.1
parse('2,45EUR'); // extra suff at the end is stripped, returns 2.45
parse('-2,543.56'); // negative numbers are OK, returns -2543.56
parse('10 345,234.21'); // returns NaN, too many different separators
parse('1.123.234,534,234'); // returns NaN, impossible to detect the decimal separator
parse('10.4,2'); // returns NaN, malformed digit groups
parse('1.123.2'); // returns NaN, also malformed digit groups

Ambiguity

What happens if a number like 1.234 is passed? What about 1,234? It's an ambiguous situation, because the library can't detect if it's an integer or a float - at least not automatically.

That's why there's a second parameter, in which you can hint at what the standard decimal separator should be. By default, that separator is . (dot).

parse('1.234'); // returns 1.234
parse('1,234'); // returns 1234
parse('1.234', ','); // returns 1234
parse('1,234', ','); // returns 1.234

Contribute

Found a bug? Feel free to open an issue or make a pull request. Always include tests, either for the bug or for your changes.

License

GNU Lesser General Public License v3.0 or later