>
> Other costs, like how require("foo/bar") can be
either foo/bar, or foo/bar.js, or foo/bar/index.js, are simply
> historical mistakes that seemed like a good idea at the time, but
> provide no value, and are now too costly to remove.
Is `index.js` considered a non-preferred method of doing package imports? I
really like it, but arguing a stable feature is pointless. I'm just curious
what the reasons were for including it, and what has changed since?
FOR SCIENCE!
--
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
