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 🙏

© 2026 – Pkg Stats / Ryan Hefner

to-safe-integer

v1.0.1

Published

Converts any JavaScript value into an integer, safely

Readme

to-safe-integer

Converts any JavaScript value into an integer, safely — never returns NaN, always falls back to a sensible default.

Installation

npm install to-safe-integer

Usage

const toSafeInteger = require('to-safe-integer');

toSafeInteger(42);            // 42
toSafeInteger(42.9);          // 42 (truncated, not rounded)
toSafeInteger("42");          // 42
toSafeInteger("42px");        // 42 (PHP-style leading digit parsing)
toSafeInteger("px42");        // 0  (no leading digit, falls back)
toSafeInteger(null);          // 0
toSafeInteger(undefined);     // 0
toSafeInteger(true);          // 1
toSafeInteger(NaN);           // 0
toSafeInteger([42]);          // 42
toSafeInteger("abc", -1);     // -1 (custom fallback)

Why not just parseInt(value)?

  • parseInt(null) returns NaN — this library returns a safe fallback instead.
  • parseInt doesn't clamp Infinity or oversized BigInt values to a safe range.
  • String parsing follows a PHP-style convention: a leading digit sequence is extracted ("42px"42), but a string that doesn't start with a digit falls back ("px42"0), unlike scanning for digits anywhere in the string.

API

toSafeInteger(value: any, fallback?: number = 0): number

Takes any value and always returns a safe integer — never throws, never returns NaN.

  • fallback — value returned when value can't be meaningfully converted. Must itself be an integer; otherwise it's silently reset to 0.

License

MIT © Toby Maxham