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

recant

v0.2.2

Published

A promise library that violates everything you know about promises.

Downloads

10

Readme

Recant

A promise library that violates everything you know about promises.

Things You Can Do

*Create promises where the resolver can reset the promise to resolve/reject again. *Create deferreds that can be reset to resolve/reject again. Again

Why on earth would you do this?

*Create a promise that always resolves with an open connection (reset the promise on conn.close or conn.err) *Pipeline dynamic dependencies through normal promise symantics

Usage

Install via NPM

$ npm install recant

Example- Promise

var recant = require('recant') ;
var promise = recant.promise(function(resolve,reject,notify,reset){
	
	var connPromise = connection.open() ;
	connPromise.then(function(conn){	
		resolve(conn) ;
		conn.on('close',reset) ;
	}).then(null,function(err){
		reject(err) ;
	})
	
})

Example- Deferred

var recant = require('recant') ;
var deferred = recant.defer() ;
var promise = deferred.promise ;

deferred.resolve(val); // as of now, all promise.then calls will resolve with a value
deferred.reset() ; // now, all promise.then calls ( against the same promise ) will be pending until resolved or rejected again
deferred.reject(err) ; // now, all promise.then calls will be rejected as the state has changed