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

minizinc-solver

v0.2.2

Published

A javascript wrapper for the MiniZinc constraints modelling language compiler and solver.

Downloads

6

Readme

minizinc-solver

A javascript library to priovide an API to a constraints solver using the MiniZinc constraints modelling language.

Why

Constraints programming provides some powerful techniques to solve certain sets of problems. Many solvers exist, but not many seem to have javascript bindings. This library provides an API to solve problems specified in the MiniZinc modelling language so that this can be more easily integrated in larger programs.

Example

var solver = require('minizinc-solver');

var problem = buildMiniZincProblemString();
solver.solve(problem).then(doSomethingWithProblemOutput);

Usage

solve(minizincProblem: string, callback: (error?, result: string) => void): void

It takes a string containing a problem specified in the MiniZinc language and returns a Promise, which may return one of three ways:

  • succeed with a string containing the output of the problem ** The format of the output is defined within the MiniZinc problem using the normal "output" command
  • succeed with null if the problem cannot be solved
  • fail with an error of the following form if there is a syntax error: { type: 'syntax_error', message: <string> }
  • fail with an error of the following form if the problem is not solved within 30 seconds: { type: 'timeout_error', message: <string> }

Typescript definitions are also provided.

solveWithTimeout(minizincProblem: string, timeoutInMillis: number, callback: (error?, result: string) => void): void

This is the same as solve except that the timeout time can be specified.

Installation

This depends on having a minizinc installation already.

  1. Install the binaries for your system here. This library uses the Gecode solver, so ensure the MiniZinc installation includes gecode binaries.
  2. Add the binaries to your PATH: export PATH=$PATH:/path/to/MiniZincIDE-2.2.3-bundle-linux/bin
  3. Install this library: npm install minizinc-solver

Testing

Tests are written using Mocha and Chai. To run them, use:

npm test

License

MIT

This project uses a MiniZinc compiler to translate constraints into a language that solvers can understand. Source code for the MiniZinc tool chain is available at http://www.minizinc.org/2.0/index.html.