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

hanachin

;;; swank-coffee.el hanachin_
;;;
;;; Copyright (c) 2010 Ivan Shvedunov. All rights reserved.
;;;
;;; Redistribution and use in source and binary forms, with or without
;;; modification, are permitted provided that the following conditions
;;; are met:
;;;
;;; * Redistributions of source code must retain the above copyright
;;; notice, this list of conditions and the following disclaimer.

takumikinjo

README.html

danlei

!!!!
!!!! .Xresources
!!!!
!!!! Time-stamp: <2010-07-25 01:22:58 danlei>
!!!!

!! xterm
XTerm*font:9x15
XTerm*background:black
XTerm*foreground:gray

danlei

module ConstituentParser
    where

import Text.ParserCombinators.Parsec
import Control.Monad
import Control.Applicative ((<$>))


symbol = oneOf "!#$%&|*+-/:<=>?@^_~"

danlei

;;;;; -*- common-lisp -*-
;;;;;
;;;;; cl-init.lisp
;;;;;
;;;;; CL initialization file. Works for CCL, Allegro, CLISP, and
;;;;; probably SBCL.
;;;;;
;;;;; Time-stamp: <2013-01-27 01:35:53 dhl>
;;;;;

danlei

----
---- loona.hs
----
---- Time-stamp: <2010-03-08 03:47:53 danlei>
----

module Loona
    where

import Text.ParserCombinators.Parsec