On Sat, May 11, 2013 at 9:05 AM, ~flow <[email protected]> wrote: > what conventions / best practices / techniques can we come up that will > allow us to 'publish in my language, run as javascript' the day that > require.extensions is gone?
What seems to be getting lost in this discussion is that require.extensions is not actually going away, certainly not in the near future and probably never. Deprecation in API-locked parts of node.js core means "you really shouldn't use this", not "we'll remove it whenever the fancy strikes us." -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
