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

restricted-number

v2.1.0

Published

A utility to keep numbers within a range.

Downloads

21

Readme

restricted-number

A nice little tool to keep your numbers in a certain range. This was primarily designed for game developers with data like HP, MP, etc that should be kept within a range.

Why use this? It saves you from typing this over and over:

if(hp <= 0) { hp=0; die(); }

if(hp > maxHp) hp = maxHp

Here's an example usage for a player:

var hp = new RestrictedNumber(0, 100, 100);

if(hp.sub(20).atMin()) die();

Or maybe for AI:

var hp = new RestrictedNumber(0, 100, 100);

if(hp.ltePercent(66)) flee();

Installation

Install with npm:

npm install --save restricted-number

Testing

From the repo root:

npm install
npm test

Functions

Function | Description -------- | ----------- new RestrictedNumber(min, max, current) | construct a RestrictedNumber set(num) | set the datum to num - mostly used internally add(num) | add num to the datum sub(num) | subtract num from the datum addOverMaximum(num) | add num to both the datum and the range subUnderMinimum(num) | subtract num from both the datum and the range toMaximum() | set the datum to the max value toMinimum() | set the datum to the min value atMaximum() | returns true if the datum is at the maximum atMinimum() | returns true if the datum is at the minimum gt(num) | returns true if the datum is greater than num gte(num) | returns true if the datum is greater than or equal to num lt(num) | returns true if the datum is less than num lte(num) | returns true if the datum is less than num setToPercent(perc) | set the datum to be at perc (the range between min and max) addPercent(perc) | add perc of the datum's maximum value to the datum subPercent(perc) | subtract perc of the datum's maximum value from the datum asPercent() | get the value of the datum as a percentage gtPercent(perc) | returns true if datum as a percentage of maximum is greater than perc gtePercent(perc) | returns true if datum as a percentage of maximum is greater than or equal toperc ltPercent(perc) | returns true if datum as a percentage of maximum is less than perc ltePercent(perc) | returns true if datum as a percentage of maximum is less than or equal to perc