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

@leptonite/parse-int-strict

v1.0.0

Published

strict replacement for parseInt

Downloads

2,121

Readme

@leptonite/parse-int-strict

@leptonite/parse-int-strict provides the function parseIntStrict which parses a string into an integer. It is much stricter than parseInt which means it rejects a lot of inputs that parseInt accepts.

Motivation

I used to use parseInt(someString) or parseInt(someString, 10) to parse strings containing integral numbers. And I check if parsing has been successful by checking if the result is NaN via Number.isNaN(result).

But some day I was suprised about the behavior of parseInt: It happily acceps inputs that do not look like integral numbers to me. parseInt(someString) seems to work like “if someString is not exactly an integral number let’s just parse some part of someString that is”, but I want “if someString is not exactly an integral number let’s just reject it by returning NaN”.

While Number(someString) is stricter than parseInt(someString, 10) in some cases it’s not an alternative because it parses fractional numbers.

Examples:

| | s | parseInt(s) | parseInt(s, 10) | Number(s) | |-----------------------------|----------------------:|--------------------:|--------------------:|--------------------:| | fractional numbers | '0.5' | 0 | 0 | 0.5 | | trailing non-digits | '1a' | 1 | 1 | NaN | | trailing non-digits / hex | '0xDF' | 223 | 0 | 223 | | scientific notation | '1e2' | 1 | 1 | 100 | | leading whitespace | '\t \n \r 1' | 1 | 1 | 1 | | > Number.MAX_SAFE_INTEGER | '9007199254740993' | 9007199254740992 | 9007199254740992 | 9007199254740992 | | < Number.MIN_SAFE_INTEGER | '-9007199254740993' | -9007199254740992 | -9007199254740992 | -9007199254740992 |

Although this behavior matches the spec it is just not what I want.

parseIntStrict

parseIntStrict(someString) is a stricter replacement for parseInt(someString, 10). It returns NaN in all examples above. There are in fact even more cases where it returns NaN.

To be more specific:

  • parseIntStrict(someString) returns an integral number (let’s call it int) if and only if all of the following is true:
    • someString is exactly equal to int.toString().
    • int is within the range [Number.MIN_SAFE_INTEGER .. Number.MAX_SAFE_INTEGER].
  • In all other cases parseIntStrict(someString) returns NaN.
  • If someString is not of type string, than the behavior of parseIntStrict(someString) is not defined.

It follows in particular:

  • parseIntStrict(someString) always returns either an integral number or NaN, it never throws.
  • If parseIntStrict(someString) returns an integral number, than it returns the same number as parseInt(someString, 10).