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

hextor

v0.1.4

Published

God of Conflicts, resolving your Orchestrate conflicts so you don't have to.

Downloads

11

Readme

Hextor

The God of Conflicts has arrived, to resolve yours!

Build Status Coverage Status

NPM

Resolves database conflicts in systems that might have them, like Orchestrate.

Install

To install Hextor, you'll need node.js. Once you have it, run this in terminal:

npm install --save hextor

Usage

var hextor = require('hextor');

var resolver = hextor({
  api_key: 'your_orchestrate_api_key',
  collection: 'your_orchestrate_collection',
  on_conflict: function (conflict, done) {
    resolve(conflict)
    .then(done.bind(null, undefined))
    .fail(done);
  }
});

resolver.on('conflict.success', console.log);

Now whenever the resolver successfully resolves a conflict, it will print a message.

Options

{
  api_key: process.ORCHESTRATE_API_KEY,
  collection: process.ORCHESTRATE_COLLECTION,
  on_conflict: function (conflict, done) {
    // see `default.js` for more info
  }
}

Events

  • connect: Emitted when Hextor begins processing conflicts.
  • conflict: Emitted when a conflict is detected, resolved, or generates an error.
  • conflict.start: Emitted when a conflict is detected.
  • conflict.resolved: Emitted when a conflict is resolved.
  • conflict.error: Emitted when resolving a conflict experiences an error.
  • error: Emitted when Hextor's connection to Orchestrate experiences an error.
  • drain: Emitted when there are no more conflicts left to process.

Usage as Daemon

You can also run Hextor as a daemon, so it will continue watching your Orchestrate collection autonomously. To start, just do:

sudo npm install -g hextor
export ORCHESTRATE_API_KEY=...
export ORCHESTRATE_COLLECTION=...
# modify defaults.js with your resolution strategies
hextor
# Now watching [collection] for conflicts...

Usage on Heroku

To deploy Hextor on Heroku, so it will watch your collection while you corner the global market on toe socks, you'll need the heroku toolbelt. Then:

git clone https://github.com/orchestrate-io/hextor.git
cd hextor
heroku create [app-name]
heroku config:set ORCHESTRATE_API_KEY=...
heroku config:set ORCHESTRATE_COLLECTION=...
git push heroku master

Now your app is running on Heroku! Since there are no worker dynos by default, let's start one:

heroku ps:scale worker=1 web=0

Tests

The tests require a valid API key to run. To set it, do this:

export ORCHESTRATE_API_KEY=YOUR_API_KEY

Then, run the tests:

npm test

License

ISC, yo.