@ry has okayed this change
Can someone explain the reason for this change? I'm sure there's a good one, but I can't find it.
The node docs explain some of the problems. The 0.4 docs should probably start saying that it IS gone in 0.5. http://nodejs.org/docs/v0.4.10/api/modules.html#_Note_Please_Avoid_Modifying_require.paths_
Close #1348 Remove require.paths
Module.globalPaths is still set to a read-only copy of the global
include paths pulled off of the NODE_PATH environment variable.
It's important to be able to inspect this, but modifying it no longer
has any effect.