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

finitedomain

v3.0.0

Published

A fast feature rich finite domain solver

Downloads

49

Readme

finitedomain Build Status

Finite domain constraint solver, originally based on FD.js.

This is very much a WIP.

API is bound to change, consider yourself warned.

Installing

npm install finitedomain

Usage

Find all numbers between 10 and 20 that are bigger than 14 and smaller than 17 and not 16. Contrived? Nah.

import Solver from 'finitedomain';

let solver = new Solver();

solver.decl('A', [10, 20]);
solver.gt('A', 14);
solver.lt('A', 17);
solver.neq('A', 16);
solver.solve();

console.log(solver.solutions); // -> [{A: 15}]

For other details see the extensive test suite.

Tasks

There are a few grunt tasks and bash scripts hooked up to npm. This repo also uses git hooks for pre- and post commit hooks.

As a general rule, ./build is used for any temporary output, including code coverage reports and temporary build files when producing a dist.

Then ./dist only contains final builds (./dist/finitedomain.dist.min.js and for some tasks ./dist/browser.js).

Note that both ./build and ./dist are cleared at the start of almost every (grunt) task.

(These tasks obviously require an npm install)

Grunt tasks:

  • grunt clean: removes ./dist and ./build
  • grunt build: a direct alias for dist
  • grunt dist: lint, test, build, and minify to produce a real dist build
  • grunt distq: create a dist but skip linting, testing, and code coverage
  • grunt distperf: same as grunt distq but also copies the dist to ./dist/browser.js, can be used in conjunction of distheat and distbug while maintaining the same path to browser.js.
  • grunt distheat: creates a dist but instead of minification as the last step it beautifies. Used for HeatFiler, a count based heatmap profiler. Copies to browser.js.
  • grunt distbug: creates a build without removing test artifacts or minification. In case you need proper stack traces in other projects.
  • grunt coverage: runs all tests in the code coverage tool
  • grunt test: runs linting and all tests
  • grunt testq: runs tests without linting
  • grunt watch:q: runs distq whenever a file changes
  • grunt watch:b: runs distbug whenever a file changes
  • grunt watch:p: runs distperf whenever a file changes

Bash / npm scripts:

  • npm run lint: run eslint with dist config (slightly stricter than dev). Exits non-zero if it fails.
  • npm run lintdev: run eslint with dev config (allows console.log, debugger, etc). No non-zero exit for failures.
  • npm run lintfix: runs eslint in the fix mode