HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
node-js-libs
chain.js
JavaScript2011–2011
node-js-libs / chain.js

chain.js

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
146GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2011-01-25 21:47:48 UTC to 2011-03-02 22:36:20 UTC. Weeks start Monday, UTC.

012011-01-24 00:00:00 UTC to 2011-01-31 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsJan 242011-01-31 00:00:00 UTC to 2011-02-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-02-07 00:00:00 UTC to 2011-02-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsFeb 72011-02-14 00:00:00 UTC to 2011-02-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-02-21 00:00:00 UTC to 2011-02-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2011-02-28 00:00:00 UTC to 2011-03-07 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 28

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 242011-01-24 00:00:00 UTC2011-01-31 00:00:00 UTC110
Jan 312011-01-31 00:00:00 UTC2011-02-07 00:00:00 UTC000
Feb 72011-02-07 00:00:00 UTC2011-02-14 00:00:00 UTC000
Feb 142011-02-14 00:00:00 UTC2011-02-21 00:00:00 UTC000
Feb 212011-02-21 00:00:00 UTC2011-02-28 00:00:00 UTC000
Feb 282011-02-28 00:00:00 UTC2011-03-07 00:00:00 UTC101

What Hacker News says

2 sources
There are many many attempts at solving this problem, both libraries and preprocessors. None seem to satisfy a large audience, most people seem to deal with the callback nesting and hope to avoid cases where it gets super ugly. I have a lot bookmarked on github, these are mostly libraries. https://github.com/coolaj86/futures https://github.com/substack/node-seq https://github.com/marcuswestin/fun https://github.com/creationix/step https://github.com/chriso/chain.js https://github.com/substack/node-chainsaw https://github.com/caolan/async https://github.com/kriszyp/promised-io https://github.com/kriszyp/node-promise https://github.com/technoweenie/node-chain-gang https://github.com/creationix/do https://github.com/willconant/flow-js https://github.com/creationix/conductor Some branches of CoffeeScript are also trying to ease the pain. Defe
Read the rest
r keyword didn't make it into CoffeeScript main. My impression is CoffeeScript makes callback hell less ugly anyway, so there is less need for adding a complex language feature that generates unreadable JavaScript.
In Three Routes to Spaghetti-Free Javascript

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.