eldargab

var Flow = require('make-flow')
// definition
var app = Flow()
.def('sum1', function (done) {
  add(1, 2, done)
})
.def('sum2', function (done) {
  add(3, 4, done)
})
.def('result', function (sum1, sum2, done) {

eldargab

#!/usr/bin/env sh

# Library version

VERSION="0.7.3"
N_PREFIX=${N_PREFIX-/usr/local}
VERSIONS_DIR=$N_PREFIX/n/versions

#
# Log the given <msg ...>

eldargab

function git_branch {
  git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e 's/* \(.*\)/\ \(\1\)/'
}

PS1="\W\$(git_branch) $ "

eldargab

function throttle (fn, timeout) {
  var ctx, args, wait = false

  return function () {
    if (wait) {
      ctx = this
      args = arguments
      return
    }
    wait = true

eldargab

Thoughts on using mocking, spying libraries for testing.

While using sinon extensively I realized that in most cases it's better to write assertions and define behaviors just right in a fake function:

it('Should list dir contents', function (done) {
  fs.readdir('dir', function (err, list) {
    should.not.exist(err)
    list.should.eql(['a', 'b', 'c'])
    done()

eldargab

var Benchmark = require('benchmark')

var suite = new Benchmark.Suite

suite
.add('push', function () {
  var a = []
  a.push("Lorem")
  a.push("ipsum")
  a.push("dolor")

eldargab

param(
    $file,
    $global
)

function camelize ($s) {
    ($s -Split "[\-_]", 0, "RegexMatch" | foreach {
        $_.Substring(0, 1).toUpper() + $_.Substring(1)
    }) -Join ""
}