| /**package | |
| * { "name": "npm-test-single-file" | |
| * , "main": "index.js" | |
| * , "version": "1.2.3" | |
| * , "description":"No package.json in sight!" | |
| * , "dependencies": { "minimatch": "*" } | |
| * } | |
| **/ | |
| module.exports = "I'm just a lonely index, naked as the day I was born." |
Here's how this works:
git_hooks/ directory in your project, with these two files (plus other hooks if you want, written in a similar style)."npm" to your devDependencies in package.json, so that the pre-commit hook can do its magic.test and lint scripts to your package.json, e.g. "scripts": {
"test": "mocha",
"lint": "jshint ./lib --show-non-errors"
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.
On Windows, paths are constructed with backslashes instead of forward slashes. So if you do your directory manipulation
| !function (window) {"use strict"; | |
| // by WebReflection - WTFPL License | |
| var | |
| prefixes = "r webkitR mozR msR oR".split(" "), | |
| process = "process", | |
| nextTick = "nextTick", | |
| i = 0, | |
| p = window[process] || (window[process] = {}) | |
| ; | |
| while (!p[nextTick] && i < prefixes.length) |
| <!DOCTYPE html> | |
| <!--[if lt IE 7 ]> <html lang="en" class="ie ie6"> <![endif]--> | |
| <!--[if IE 7 ]> <html lang="en" class="ie ie7"> <![endif]--> | |
| <!--[if IE 8 ]> <html lang="en" class="ie ie8"> <![endif]--> | |
| <!--[if IE 9 ]> <html lang="en" class="ie ie9"> <![endif]--> | |
| <!--[if (gt IE 9)|!(IE)]><!--> <html lang="en"> <!--<![endif]--> | |
| <head> | |
| <meta charset="utf-8"> | |
| <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> |
| alias branches='for k in `git branch|sed s/^..//`;do echo -e `git log -1 --pretty=format:"%Cgreen%ci %Cblue%cr%Creset" "$k"`\\t"$k";done|sort' |
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.
| // pre-ES5 IE version | |
| var dict = (function() { | |
| var PROPERTY_KEYS = [ | |
| "hasOwnProperty", | |
| "isPrototypeOf", | |
| "propertyIsEnumerable" | |
| "valueOf", | |
| "toString", | |
| "toLocaleString", | |
| "constructor" |
| /** | |
| * so here the thing ... you go in your github page | |
| * as example I go here: https://github.com/WebReflection | |
| * you open your console | |
| * you copy and paste this shit | |
| * then you write and execute in the console | |
| * write("Hi There!"); | |
| * NOTE: Pixel Font from a 2006 project of mine :-) http://devpro.it/pixelfont/ | |
| */ | |
| function write(text, color, start) { |
| // a sort-of-polyfill for `currentThis` as proposed in: https://gist.github.com/getify/5253319 | |
| function lookupFn(oThis,fn) { | |
| var ptr = oThis, i, keys; | |
| while (ptr) { | |
| keys = Object.keys(ptr); | |
| for (i=0; i<keys.length; i++) { | |
| if (ptr[keys[i]] === fn) { | |
| return ptr; | |
| } | |
| } |