tj

/**
 * Module dependencies.
 */

var pkg = require('../package');
var env = process.env.NODE_ENV || 'development';

/**
 * Return setting `name`.
 *

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.

mikeal

JSON._dateReviver = function (k,v) {
  if (v.length !== 24 || typeof v !== 'string') return v
  try {return new Date(v)} 
  catch(e) {return v}
}

JSON.parseWithDates = function (obj) {
  return JSON.parse(obj, JSON._dateReviver);
}

jlong

var parser = document.createElement('a');
parser.href = "http://example.com:3000/pathname/?search=test#hash";

parser.protocol; // => "http:"
parser.hostname; // => "example.com"
parser.port;     // => "3000"
parser.pathname; // => "/pathname/"
parser.search;   // => "?search=test"
parser.hash;     // => "#hash"
parser.host;     // => "example.com:3000"

indexzero

npmcount output for groups of node.js thought leaders

• Nodejitsu
• Browserling
• LearnBoost
• Node.js Core team

This list has been computed using a silly tool I developed on a lark called npmcount:

• Search npm for packages belonging to a set of users.

madrobby

# before this file is loaded, a locale should be set:
# 
# In a browser environment, you can use:
# ```<script>__locale='en';</script>```
#
# In a server environment (specifically node.js):
# ```global.__locale = 'en';```

# normalize in-app locale string to "en" or "de-AT"
parts = @__locale.split('-')

ded

var express = require('express')
  , app = express.createServer()

require('./config/routes').initialize(app)

fhemberger

##Using libuv and http-parser to build a webserver Ryan Dahl, @ryah
http://vimeo.com/24713213
Source, Part I: http://t.co/utoIM93
Source, Part II: http://bit.ly/iBgnIA

##Node.js on windows Bert Belder
http://2bs.nl/nodecamp.pdf

gf3

#!/usr/bin/env zsh
# git-feature
# Written by: Gianni Chiappetta <gianni@runlevel6.org>
# Requires: git 1.7.5+, zsh 4.3.11+
# Screenshot: http://cloud.gf3.ca/6TPb

function c_list { echo  "  \033[1;32m✔\033[0m $1"; }

function e_list { echo  "  \033[1;31m✖\033[0m $1"; }

joemccann

The idea is to have nginx installed and node installed. I will extend this gist to include how to install those as well, but at the moment, the following assumes you have nginx 0.7.62 and node 0.2.3 installed on a Linux distro (I used Ubuntu).

In a nutshell,

1. nginx is used to serve static files (css, js, images, etc.)
2. node serves all the "dynamic" stuff.

So for example, www.foo.com request comes and your css, js, and images get served thru nginx while everything else (the request for say index.html or "/") gets served through node.

3. nginx listens on port 80.