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

node-transactions

v1.1.1

Published

Transactions engine for node.js

Downloads

28

Readme

Node Transactions

Build Status Coverage Status npm

Usage

Examples of code are shown in test/index.spec.js

In case you are already using generators-yields functions - you are completely set up.

If you are writing classic async-callback code - you would probably like to look at thunkify package.

##API

Context

The first thing you need is the context object, which would have all required data for tasks execution.

let context = {
	lannisters: false,
	starks: true
}

Task

The main brick of the Node Transactions module is a task:

task = {
	name: 'westeros',
	perform: function *doYourJob() { ... },
	rollback: function *revertChanges() { ... }
};

Launching

When you have prepared bunch of tasks and context - simply launch Transactions engine:

let result = yield new Transactions([task, nextTask, ...], context);

Result

result would have next properties:

  1. result.success - enum: [true, false]
  2. result.context[task.name].performResult - the result of successful execution of tesk.perform
  3. result.error - the first and only task.perform error (only if result.success === false)
  4. result.rollbackErrors - array of possible task.rollback errors

Storing transactions' data

To store the intermediate transaction's data, you need to pass into the context your own implementation of storeTransactionState, which would get next args:

function *storeTransactionState(name, phase, context) { ... }
context.storeTransactionState = storeTransactionState;

Issues

Any bugs or improvements are appreciated and could be posted at https://github.com/ceoworks/node-transactions/issues