Scott Yu scootcho

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

S3 Static Sites

What this will cover

Host a static website at S3
Redirect www.website.com to website.com
Website can be an SPA (requiring all requests to return index.html)
Free AWS SSL certs
Deployment with CDN invalidation

Resources

Theming Ant Design with Sass and Webpack

This is a solution on how to theme/customize Ant Design (which is written in Less) with Sass and webpack. Ant itself offers two solutions and a related article on theming, but these are only applicable if you use Less, the antd-init boilerplate or dva-cli.

What this solution offers:

use a single sass-file to customize (no duplicate variables for your project and Ant)
hot reload compatibility
no dependencies on outdated npm modules
easy integration with your existing webpack setup (webpack 3+ tested)

Keyboard-only Mac Cheatsheet

Hi, I'm Lorna and I don't use a mouse. I have had RSI issues since a bad workstation setup at work in 2006. I've tried a number of extra hardware modifications but what works best for me is to use the keyboard and only the keyboard, so I'm in a good position and never reaching for anything else (except my coffee cup!). I rather unwisely took a job which required me to use a mac (I've been a linux user until now and also had the ability to choose my tools carefully) so here is my cheatsheet of the apps, tricks and keyboard shortcuts I'm using, mostly for my own reference. Since keyboard-only use is also great for productivity, you may also find some of these ideas useful, in which case at least something good has come of this :)

Apps List

There's more detail on a few of these apps but here is a quick overview of the tools I've installed and found helpful

Tool	Link	Comments

Handling Errors

Express.js makes it a breeze to handle errors in your routes.

Express lets you centralizes your error-handling through middleware.

Let's look at patterns for how to get the most out of your error-handling.

First, our error-handling middleware looks like this:

	var mongoose = require('./index')
	, TempSchema = new mongoose.Schema({
	salutation: {type: String, enum: ['Mr.', 'Mrs.', 'Ms.']}
	});

	var Temp = mongoose.model('Temp', TempSchema);

	console.log(Temp.schema.path('salutation').enumValues);
	var temp = new Temp();
	console.log(temp.schema.path('salutation').enumValues);

	require("express-namespace");
	var express = require("express"),
	fs = require("fs"),
	cons = require("consolidate"),
	app = express(),
	passport = require("passport"),
	mongoose = require("mongoose");

	// 30 days for session cookie lifetime
	var SESSION_COOKIE_LIFETIME = 1000 * 60 * 60 * 24 * 30;

	var express = require('express');
	var cookieParser = require('cookie-parser');
	var session = require('express-session');
	var flash = require('express-flash');
	var handlebars = require('express-handlebars')

	var app = express();
	var sessionStore = new session.MemoryStore;

	// View Engines

	// file: index.js

	var _ = require("lodash");
	var express = require("express");
	var bodyParser = require("body-parser");
	var jwt = require('jsonwebtoken');

	var passport = require("passport");
	var passportJWT = require("passport-jwt");

	//
	// Implementation using express-jwt middle
	//
	var express = require('express'),
	ejwt = require('express-jwt'),
	jwt = require('jsonwebtoken'),
	passport = require('passport'),
	bodyParser = require('body-parser'),
	LocalStrategy = require('passport-local').Strategy,
	BearerStrategy = require('passport-http-bearer').Strategy;