Joe Wang joe11051105

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

What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.

Element

Box metrics

elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
elem.clientLeft, elem.clientTop, elem.clientWidth, elem.clientHeight
elem.getClientRects(), elem.getBoundingClientRect()

	# be sure to comment out the require 'capistrano/deploy' line in your Capfile!

	# config valid only for Capistrano 3.1
	lock '3.2.1'

	set :application, 'my-cool-application'

	# the base docker repo reference
	set :name, "johns-stuff/#{fetch(:application)}"

	# 先安裝 gem
	gem install httpclient

	require "httpclient"

	request = HTTPClient.new
	request.set_basic_auth("https://api.github.com/user", "joe11051105", "password")
	request.get "http://api.github.com/joe11051105/repos"

	rm(list = ls())
	iter = 10000
	p = runif(iter)
	coord = matrix(c(0, 0), ncol = 1)
	df = rbind(data.frame(), t(coord))
	for (i in 1:iter) {
	indicator = runif(1, 0, 1)
	if (indicator <= 0.05) {
	m = matrix(c(0, 0, 0, 0.16), nrow = 2, ncol = 2)
	const = matrix(c(0, 0), ncol = 1)

	// Use Gists to store code you would like to remember later on
	console.log(window); // log the "window" object to the console