I know that, to quote my previous e-mail:
> The issue is not about the extra 4 chars ("lib/") but about having
different require paths depending on the environment, code will be less
portable.
I don't want `require("kitchen-sink/lib/foo")` on one environment and
`require("kitchen-sink/foo")` on another, the lack of a "directories.lib"
setting is hurting compatibility/flexibility. It's a shame to have to
follow the less flexible system just because it is the most popular, this
is not how "standards" should be created.
On Friday, January 18, 2013 1:18:59 AM UTC-2, Raynos wrote:
>
> require("kitchen-sink/lib/foo");
>
> You can already require files.
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
