Jonas Hermsmeier jhermsmeier

Node.js core does its best to treat every platform equally. Even if most Node developers use OS X day to day, some use Windows, and most everyone deploys to Linux or Solaris. So it's important to keep your code portable between platforms, whether you're writing a library or an application.

Predictably, most cross-platform issues come from Windows. Things just work differently there! But if you're careful, and follow some simple best practices, your code can run just as well on Windows systems.

Paths and URLs

On Windows, paths are constructed with backslashes instead of forward slashes. So if you do your directory manipulation

Locate the section for your github remote in the .git/config file. It looks like this:

[remote "origin"]
	fetch = +refs/heads/*:refs/remotes/origin/*
	url = [email protected]:joyent/node.git

Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this:


	var levenshtein = function(str1, str2) {
	str1 = str1.split("");
	str2 = str2.split("");
	var distance = [],
	l = str1.length,
	m = str2.length,
	i, j;

	for( i = 0; i <= l; i++ ) {

	#!/usr/bin/env sh

	##
	# This is script with usefull tips taken from:
	# https://github.com/mathiasbynens/dotfiles/blob/master/.osx
	#
	# install it:
	# curl -sL https://raw.github.com/gist/2108403/hack.sh \| sh
	#

	// Creating a grammatical pattern for real numbers using XRegExp.build

	/*
	* Approach 1: Make all of the subpatterns reusable
	*/

	var lib = {
	digit: /[0-9]/,
	exponentIndicator: /[Ee]/,
	digitSeparator: /[_,]/,

	var GO = 'GO',
	OK = 'OK',
	SIGN = 'SIGN',
	LZERO = 'LZERO',
	INT = 'INT',
	FRAC = 'FRAC',
	FDIG = 'FDIG',
	EXP = 'EXP',
	XSIGN = 'XSIGN',
	EDIG = 'EDIG',

	var stream = require("fake-stream-lib"),
	Emitter = require("events").EventEmitter,
	util = require("util");


	// Today...

	function Device( opts ) {

	this.value = null;

	<!DOCTYPE html>
	<html>
	<head>
	<meta charset=utf-8 />
	<title>Hello</title>
	<link rel="stylesheet" href="styles.css">
	</head>
	<body>
	Hello World
	</body>

	for i in $HOME/local/*; do
	[ -d $i/bin ] && PATH="${i}/bin:${PATH}"
	[ -d $i/sbin ] && PATH="${i}/sbin:${PATH}"
	[ -d $i/include ] && CPATH="${i}/include:${CPATH}"
	[ -d $i/lib ] && LD_LIBRARY_PATH="${i}/lib:${LD_LIBRARY_PATH}"
	[ -d $i/lib ] && LD_RUN_PATH="${i}/lib:${LD_RUN_PATH}"
	# uncomment the following if you use macintosh
	# [ -d $i/lib ] && DYLD_LIBRARY_PATH="${i}/lib:${DYLD_LIBRARY_PATH}"
	[ -d $i/lib/pkgconfig ] && PKG_CONFIG_PATH="${i}/lib/pkgconfig:${PKG_CONFIG_PATH}"
	[ -d $i/share/man ] && MANPATH="${i}/share/man:${MANPATH}"

	#!/bin/bash
	# License: Public Domain.
	# Author: Joseph Wecker, 2012
	#
	# -- DEPRICATED --
	# This gist is slow and is missing .bashrc_once
	# Use the one in the repo instead! https://github.com/josephwecker/bashrc_dispatch
	# (Thanks gioele)
	#
	# Are you tired of trying to remember what .bashrc does vs .bash_profile vs .profile?