I think this would be more of a design choice, overhead to requiring
modules is minimal - if the same module in a parent module is
required in a child module I believe its already cached, plus
requiring is a one time only event at the beginning of execution the
already minimal cost of requiring i
I am very wary of the module system needing to load modules, the less
external dependencies the better. That being said, you could use the built
in util functions, but then if a user application modifies the util
functions it will cause problems in module.js; tradeoffs.
--
--
Job Board: http:
