ToanTranX

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:

var Article = require('../../../models/article');

Those suck for maintenance and they're ugly.

Possible solutions

ToanTranX

var graphql = require('graphql');

export function Edge(itemType: any) {
    return new graphql.GraphQLObjectType({
        name: "Edge",
        description: "Generic edge to allow cursors",
        fields: () => ({
            node: { type: itemType },
            cursor: { type: graphql.GraphQLString }
        })

ToanTranX

// EaselJS still has some problems compiling with Webpack/CommonJS as of this
// publishing (01/23/2016), which makes it difficult to write modularity
// in ES6 for it. However, it's not that hard to work around:
import { Car, Mustang } from './Cars';

let createjs = window.createjs; // local reference to createjs and bypasses the current module issues
let stage = new createjs.Stage('car_canvas');
let car = new Car({
  color: '#0081c9',
  id: 'car1',

ToanTranX

package demo

import akka.actor.{Props, ActorSystem}
import akka.persistence.PeristentActor

object PingPong extends App {
  case object Ball         // The Command
  case object BallReceived // The Domain Event, represents a Fact, something that have already happened

  class Ping extends PeristentActor {