lygaret

define(function(require) {
    var React = require('react');

    var paramRegex  = /__(\d)+/;
    var parser      = new DOMParser();
    var errorDoc    = parser.parseFromString('INVALID', 'text/xml');
    var errorNs     = errorDoc.getElementsByTagName("parsererror")[0].namespaceURI;

    // turns the array of string parts into a DOM
    // throws if the result is an invalid XML document.

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

robertkowalski

The licenses in the npm-registry from their package.json, from the latest version of each module

23.11.2013

[ { key: 'undefined', value: 27785 },
  { key: 'MIT', value: 20811 },
  { key: 'BSD', value: 5240 },
  { key: 'BSD-2-Clause', value: 621 },
  { key: 'Apache 2.0', value: 263 },
  { key: 'GPL', value: 233 },

RubaXa

/**
 * Watcher leaks for jQuery
 * RubaXa <[email protected]>
 * MIT Licensed.
 *
 * API:
 * 	$.leaks.get();
 * 	$.leaks.watch();
 * 	$.leaks.unwatch();
 * 	$.leaks.remove();

brettz9

/*globals DOMImplementation, ActiveXObject */
if (!DOMImplementation.prototype.createDocument) {

(function () {
'use strict';

var i, docObj, docObjType,
    docObjs = [
        'MSXML6.DOMDocument', 'MSXML5.DOMDocument', 'MSXML4.DOMDocument',
        'MSXML3.DOMDocument', 'MSXML2.DOMDocument.5.0', 'MSXML2.DOMDocument.4.0',

monolithed

/*
* Range
* @author: Alexander Guinness
* @version: 1.0
* @license: MIT
* @date: 7/20/12 9:28 PM
*/

function range (from, to, step) {
	var array = [];

Calvein

body#-webkit-web-inspector #main{background-color:#002b36!important}body#-webkit-web-inspector #main .panel.network,body#-webkit-web-inspector #main .panel.timeline,body#-webkit-web-inspector #main .panel.profiles,body#-webkit-web-inspector #main .panel.audits,body#-webkit-web-inspector #main .panel.extension{background-color:#fff!important}body#-webkit-web-inspector #console-messages a:hover,body#-webkit-web-inspector #console-messages .console-formatted-function,body#-webkit-web-inspector #console-messages .console-formatted-object{color:#93a1a1!important}body#-webkit-web-inspector #console-prompt,body#-webkit-web-inspector #console-messages a,body#-webkit-web-inspector #console-messages .console-message,body#-webkit-web-inspector #console-messages .console-group-messages .section .header .title{color:#839496!important}body#-webkit-web-inspector #console-messages .console-formatted-null,body#-webkit-web-inspector #console-messages .console-formatted-undefined{color:#657b83!important}body#-webkit-web-inspect

emanuelez

How Fast is Git?

The web is full of benchmarks showing the supernatural speed of Git even with very big repositories, but unfortunately they use the wrong variable. Size is not important, but the number of files in the repository really is!

Why is that? Well, that's because Git works in a very different way compared to Synergy. You don't have to checkout a file in order to edit it; Git will do that for you automatically. But at what price?

The price is that for every Git operation that requires to know which files changed (git status, git commmit, etc etc) an lstat() call will be executed for every single file

Wow! So how does that perform on a fairly large repository? Let's find out! For this example I will use an example project, which has 19384 files in 1326 folders.

micho

First, install nginx for mac with "brew install nginx".

Then follow homebrew's instructions to know where the config file is.

1. To use https you will need a self-signed certificate: https://devcenter.heroku.com/articles/ssl-certificate-self
2. Copy it somewhere (use full path in the example below for server.* files)
3. sudo nginx -s reload
4. Access https://localhost/

Edit /usr/local/etc/nginx/nginx.conf:

cwarden

require "try-catch"

try {
   function()
      error('oops')
   end,

   catch {
      function(error)
         print('caught error: ' .. error)