> > i envision that i will put a standardized, constant index.js in each of my > module folders that will do the bootstrap transpiling business quite > transparently >
That's wrong because 1. That means that additional typically huge dependency must be added 2. Compiler may just don't work in a target environment. Once again and finally I'd like to clarify the claim to the core team: 1) require.extensions is an easy way to define custom executables that support additional languages, e.g. coffeenode, wispnode, sagenode, etc. Then coffeenode@1.0 relates to coffeenode@2.0 like ruby@1.8 to ruby@2.0 or like python@2 to python@3. It's hard to see what's wrong with that. 2) The above post shows that deprecation of require.extensions just fails to solve the problem it's intended to solve. -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
