creationix

var http = require('http');
var send = require('send');
var urlParse = require('url').parse;

var count = 2;
var server = http.createServer(function (req, res) {
  if (!--count) server.close(); // Only allow two connection and then exit.
  send(req, urlParse(req.url).pathname)
    .root(__dirname)
    .pipe(res);

nicolashery

var util = require('util')
  , Transform = require('stream').Transform
  , StreamCombiner = require('./streamcombiner');

var chunks1 = [];
var stream1 = new Transform();
var soFar = '';
stream1._transform = function(chunk, encoding, done) {
  chunks1.push(chunk.toString());
  var pieces = (soFar + chunk).split('\n');

mklabs

node_modules

# folders used for testing
css
img
images
test

indexzero

{
  "passfail": false,
  "maxerr": 100,

  "browser": true,
  "node": true,
  "rhino": false,
  "couch": true,
  "wsh": true,
  "jquery": true,

addyosmani

#Lessons From A JavaScript Code Review

I was recently asked to review some code for a new JavaScript application and thought I might share some of the feedback I provided as it includes a mention of JavaScript fundamentals that are always useful to bear in mind. Code reviews are possibly the single biggest thing you can do to improve the overall quality of your solutions and if you're not actively taking advantage of them, you're possibly missing out on bugs you haven't noticed being found or suggestions for improvements that could make your code better.

##Challenges & Solutions

Code reviews go hand-in-hand with maintaining strong coding standards. That said, standards don't usually prevent logical errors or misunderstandings about the quirks of a programming language. Even the most experienced developers can make these kinds of mistakes and code reviews can greatly assist with catching them.

Often the most challenging part of code reviews is actually finding an experienced developer you trust to complete

dperini

//
// Regular Expression for URL validation
//
// Author: Diego Perini
// Created: 2010/12/05
// Updated: 2018/09/12
// License: MIT
//
// Copyright (c) 2010-2018 Diego Perini (http://www.iport.it)
//