There are benefits of doing that, but they are very insignificant. I'd even advice against it because it leaves ugly stack traces, and they are hard to debug.
However, if you merge all code first (using https://github.com/crcn/sardines for example), you reduce a startup time, and that could be significant if your application is started frequently. After that if you don't care about stack traces, you can minify this large script you get and maybe save a few microseconds here and there. So, if you're writing a module, you definitely shouldn't minify anything, it won't get any performance gain. If you're writing a big command line application, you might think about it, but it's rare. For example, it won't matter for usual http server, but npm could benefit from this a lot. On Tuesday, November 12, 2013 2:58:12 PM UTC+4, Stefan Klein wrote: > > I'm wondering if there are any significant benefits of minifying module > code with uglyfyjs/google closure compiler. > Did anybody test this yet? > > > -- -- 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.
