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

staltz

The introduction to Reactive Programming you've been missing

(by @andrestaltz)

---

This tutorial as a series of videos

If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.

---

dirkmc

// Config looks like this:
/*
    proxy: {
        port: 5000,
        // Indicates if there is a PROXY protocol enabled Load Balancer
        // between us and the client
        useProxyProtocol: true,
        status: {
            path: '/status.json',
            // How many times can a host fail to respond before it is

ericelliott

Essential JavaScript Links

I no longer mantain this list. There are lots of other very comprehensive JavaScript link lists out there. Please see those, instead (Google "awesome JavaScript" for a start).

datchley

/**
 * Primary application logic for our Functional Programming blog example
 * See related blog series at: http://www.datchley.name/tag/functional-programming/
 * Version: 2.0
 */
 
// A simple, resuable comparison for '>='
function greaterThanOrEqual(a, b) {
  return a >= b
}

realadeel

var AWS = require('aws-sdk');
var sns = new AWS.SNS();
var GoogleMaps = require('googlemaps');
var GooglePlaces = require('node-googleplaces');
var weather = require('openweather-apis');
var stripe = require('stripe')(STRIPE_SECRET_KEY);
var googleConfig = { key: GOOGLE_API_KEY };
var maps = new GoogleMaps(googleConfig);
var places = new GooglePlaces(googleConfig.key);
var direction_params = {

lobster1234

Working with Serverless and Java - Part 1

In this tutorial, we will create and deploy a java-maven based serverless service using the serverless project (https://serverless.com/). In this part we will not modify any code, or even look at the generated code. We will focus on the deployment and the command line interface provided by serverless. Serverless is a node.js based framework that makes creating, deploying, and managing serverless functions a breeze. We will use AWS as our FaaS (Function-as-a-Service) provider.

Pre-requisites

Here is what the setup on my Mac looks like (Sierra)

• brew (1.1.10) - you will need this if you do not have node/npm installed already.
• node (v7.6.0)
• npm (4.1.2)
• Apache Maven (3.2.5)