eligrey

/*
 * object.watch polyfill
 *
 * 2012-04-03
 *
 * By Eli Grey, http://eligrey.com
 * Public Domain.
 * NO WARRANTY EXPRESSED OR IMPLIED. USE AT YOUR OWN RISK.
 */

alkema

set :application, "appname"
set :deploy_to, "/var/www"

set :scm, :git
set :repository, "[email protected]:user/app.git"

default_run_options[:pty] = true
set :user, "www-data"
set :domain, "foo.tld"
set :normalize_asset_timestamps, false

fatihacet

var pubsub = {};
(function(q) {
    var topics = {}, subUid = -1;
    q.subscribe = function(topic, func) {
        if (!topics[topic]) {
            topics[topic] = [];
        }
        var token = (++subUid).toString();
        topics[topic].push({
            token: token,

benbuckman

var _ = require('underscore'),
    util = require('util');

// intercept stdout, passes thru callback
// also pass console.error thru stdout so it goes to callback too
// (stdout.write and stderr.write are both refs to the same stream.write function)
// returns an unhook() function, call when done intercepting
module.exports = function interceptStdout(callback) {
  var old_stdout_write = process.stdout.write,
      old_console_error = console.error;

domenic

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

FGRibreau

/*
  fileExistSync - Check if a file exist in NodeJS
  Twitter: @FGRibreau / fgribreau.com

  Usage: 
    var fileExistSync = require('./fileExistSync');
    
    var exist = fileExistSync('/var/folders/zm/jmjb49l172g6g/T/65b199');
    
  Support for Nodev0.6

mattberg

var baseUrl = 'https://api.parse.com/1',
    appId = 'XXXXXXXXXXXXXXX',
    apiKey = 'XXXXXXXXXXXXXX'; // make sure to use the REST API Key

var _register = function(params, lambda, lambdaerror) {
    var method = 'POST',
        url = baseUrl + '/installations',
        payload = (params) ? JSON.stringify(params) : '';
            
    _helper(url, method, payload, function(data, status) {

cbednarski

[
  { "keys": ["ctrl+shift+t"], "command": "open_terminal_project_folder" },
  { "keys": ["ctrl+tab"], "command": "next_view" },
  { "keys": ["ctrl+shift+tab"], "command": "prev_view" }
]

lfender6445

query_to_hash = function() {
  var j, q;
  q = window.location.search.replace(/\?/, "").split("&");
  j = {};
  $.each(q, function(i, arr) {
    arr = arr.split('=');
    return j[arr[0]] = arr[1];
  });
  return j;
}

branneman

Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:

const Article = require('../../../../app/models/article');

Those suck for maintenance and they're ugly.

Possible solutions