Fredrik Westmark westmark

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

1. Clone your fork:

git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

	var gulp = require('gulp'),
	watch = require('gulp-watch'),

	// This will keeps pipes working after error event
	plumber = require('gulp-plumber'),

	// linting
	jshint = require('gulp-jshint'),
	stylish = require('jshint-stylish'),

	-- `menu_click`, by Jacob Rus, September 2006
	--
	-- Accepts a list of form: `{"Finder", "View", "Arrange By", "Date"}`
	-- Execute the specified menu item. In this case, assuming the Finder
	-- is the active application, arranging the frontmost folder by date.

	on menu_click(mList)
	local appName, topMenu, r

	-- Validate our input

	Copyright 2012 Shin Suzuki<[email protected]>

	Licensed under the Apache License, Version 2.0 (the "License");
	you may not use this file except in compliance with the License.
	You may obtain a copy of the License at

	http://www.apache.org/licenses/LICENSE-2.0

	Unless required by applicable law or agreed to in writing, software
	distributed under the License is distributed on an "AS IS" BASIS,