wbyoung

#!/bin/bash

set -e

JQ="jq --raw-output --exit-status"

escape-json() {
  python -c "import sys; import json; sys.stdout.write(json.dumps(sys.stdin.read().strip())[1:-1])"
}

OverZealous

/**
 * This file/module contains all configuration for the build process.
 */

/**
 * Load requires and directory resources
 */
var join = require('path').join,
	bowerrc = JSON.parse(require('fs').readFileSync('./.bowerrc', {encoding: 'utf8'})),
	bowerJSON = bowerrc.json.replace(/^\.?\/?/, './'),

timruffles

var Nothing = {Nothing: true}

function MaybeGenerator() {
  var g = arguments[arguments.length - 1]
  // list of functions that test for any "Nothing" values
  var maybes = [].slice.call(arguments,0,arguments.length - 1)

  return function(value) {
    var generator = g.apply(null,[].slice.call(arguments,1))
    var result

domenic

module.exports = and ES6 Module Interop in Node.js

The question: how can we use ES6 modules in Node.js, where modules-as-functions is very common? That is, given a future in which V8 supports ES6 modules:

• How can authors of function-modules convert to ES6 export syntax, without breaking consumers that do require("function-module")()?
• How can consumers of function-modules use ES6 import syntax, while not demanding that the module author rewrites his code to ES6 export?

@wycats showed me a solution. It involves hooking into the loader API to do some rewriting, and using a distinguished name for the single export.

This is me eating crow for lots of false statements I've made all over Twitter today. Here it goes.

dnagir

# RSpec 2.0 syntax Cheet Sheet by http://ApproachE.com

# defining spec within a module will automatically pick Player::MovieList as a 'subject' (see below)
module Player
	describe MovieList, "with optional description" do
		  
	  it "is pending example, so that you can write ones quickly"
	  
	  it "is already working example that we want to suspend from failing temporarily" do
		pending("working on another feature that temporarily breaks this one")