Tatsuya Sakamoto celestella

WebRTC コトハジメ

更新:	2024-05-20
作者:	@voluntas
バージョン:	2024.1
URL:	https://voluntas.github.io/

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

ACL / Roles + Permissions

https://github.com/djvirgen/virgen-acl Simple and elegant, create your own checks. No middleware?

https://github.com/OptimalBits/node_acl Use as middleware, create your own roles and access. Great choice.

https://github.com/tschaub/authorized Similar to connect roles... but a bit more robust? you can create roles and action, and associate many roles with that action

	/**
	* Simple node_acl example with mongoDB and expressjs
	*
	* Usage:
	* 1. Start this as server
	* 2. Play with the resoures
	*
	* Show all permissions (as JSON)
	* http://localhost:3500/info
	*

	var restify = require('restify');

	// Authentication
	var passport = require('passport');
	var LocalStrategy = require('passport-local').Strategy;
	var sessions = require("client-sessions");

	var server = restify.createServer();
	server.use(restify.queryParser());
	server.use(restify.bodyParser());