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

due-compiler

v0.0.5

Published

A compiler to transform pyramid of callback into sequence of Dues

Downloads

4

Readme

Due compiler

NPM

What is a due ?

A due is a simpler alternative to Promises in Javascript. It doesn't follow the Promise/A+ specification. Instead, it follows the error-first convention from Node.js.

Compiler

This compiler translate a javascript code using callbacks, into a javascript code using Dues.

// parent
_1(input_1, function(err, res) { // 1
  _2(input_2, function(err, res) { // 2 
    _3(input_3, function(err, res) { // 3

    });
  });
});

into

// parent
_1(input_1)
.then( funciton(err, res) { // 1
  return _2(input_2)
})
.then( funciton(err, res) { // 2
  return _3(input_3)
})
.then( funciton(err, res) { // 3
  
})
  • It doesn't replace the libraries, you have to replace the vanilla libraries with due-compatible libraries. You can use the mock method from the npm due package, to make an asynchronous call due-compatible.

  • It doesn't spot asynchronous functions, you have to provide a method to filter asynchronous from synchronous functions. The console client, and the web client provide an interactive interface to do that. You can automate this process with your own method.

Usage

Console client

./bin/compiler <source> [<target>]

If target is not specified, the compiler write to a file named <source path and base name>-due.js.

Web client

The compiler is available online, as a standalone webpage.

Node.js API

It is possible to use the compiler as a node.js library.

var due_compiler = require('due-compiler');

due_compiler(code, filterRP, callback);

filterRP must be a function to filter synchronous from asynchronous function calls. The asynchronous function calls are called rupture points, because they allow the transformation.

function filterRP(err, potentialRP, callback) {

  var actualRP = potentialRP.filter(function(rp) {
    // ... return rp.isAsynchronous
  })

  callback(null, actualRP);

}

Browser API

It is possible to use the compiler in the browser, using Browserify. The API is the same as for node.js.

The following command create a bundle to include in your webpage.

browserify pages/scripts/client.js > pages/scripts/script.js
<script src="scripts/script.js"></script>
<script type="text/javascript">
  var compiler = window.compiler;
</script>

Internals

Compilation steps

1 - build the trees of direct child asynchronous calls An asynchronous calls callback can call many asynchronous calls.

2 - Build the chains from the tree If a callback call many asynchronous calls, the chain can continue with no more than one of them. The other ones are turned into different chains.

3 - Inside a chain, find and list the shared identifiers. these identifiers need to be moved to a parent scope.

4 - Modify the code accordingly to these modifications