ThadeuLuz

import React, { PropTypes } from 'react';
import MDialog from 'material-ui/Dialog';
import './dialog.css';

const Dialog = props => (
  <MDialog
    {...props}

    repositionOnUpdate={false}
    autoDetectWindowHeight={false}

inopinatus

console.log('Loading function');

const https = require('https');
const url = require('url');
const slack_url = 'https://hooks.slack.com/services/...';
const slack_req_opts = url.parse(slack_url);
slack_req_opts.method = 'POST';
slack_req_opts.headers = {
    'Content-Type': 'application/json'
};

maximilianschmitt

How to add an Istanbul code coverage badge to your GitHub repository

This post has moved to my personal blog: http://maximilianschmitt.me/posts/istanbul-code-coverage-badge-github/

vgeshel

console.log('Loading function');

const https = require('https');
const url = require('url');
// to get the slack hook url, go into slack admin and create a new "Incoming Webhook" integration
const slack_url = 'https://hooks.slack.com/services/...';
const slack_req_opts = url.parse(slack_url);
slack_req_opts.method = 'POST';
slack_req_opts.headers = {'Content-Type': 'application/json'};

obolton

AWS ELB with Node.js and WebSockets

This assumes that:

• You are using Nginx.
• You want to accept incoming connections on port 80.
• Your Node.js app is listening on port 3000.
• You want to be able to connect to your Node.js instance directly as well as via the load balancer.

####1. Create load balancer

etiennea

packages:
  yum:
    git: []
    gcc: []
    make: []
    openssl-devel: []
    ImageMagick: []

option_settings:
  - option_name: NODE_ENV

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