Splitting this from Build tool. What I want: -given entry.js, the tool has to resolve it's dependencies inspecting require, recursivly including all relevant files -conviently do jslint/hint checks as codestrings are already loaded -possibility to minify for production -filewatching and possibly caching
To sum up for now: -browserify <https://github.com/substack/node-browserify>: still the mightiest for this task I've seen. Does basically all mentionend above. But it's "just works(TM)" just won't work for me. I keep running into bugs or bad documentation. -browserbuild <https://github.com/LearnBoost/browserbuild>: KISS implementation, combining all available source files and a simple browserside require() replacement -pakmanager <https://github.com/coolaj86/node-pakmanager>: like browserbuild, but with ender.js require() implementation. The last two don't satisfy my needs. Lazy- or Preload modules: Also I noticed that browserify and browserbuild use lazy module loading. So the source of each file is wrapped in a function which is invoked the first time a module is required. I had implemented this diffrently before: I just wrapped a closure around each file source to execute when it's loaded. I think it's better to preload all libraries and prototypes like I did, although I'm not sure if this would have impact on the responsiveness of the interface. Better a long load in the beginning that lags in the first minutes. The algorithm for preloading addintionally has to include some sorting to execute the files in the right order. regards, Ph I wrote: > Yeah, of course. But browserify does this better as anything else, and > it's IMO the most important part of the JavaScript build process. So a > lot of focus should go on this and every single nodejs build tool should > support it by default. > > Just specifying one file to start this assembly and then adding all > required files and modules recursivly seems to be the right approch for > me. Right? > Running that through jslint/hint and running tests aswell as diffrent > dev/production versions seems to me all a build tool for nodejs needs to do. > I don't see any build tool available which does this well enough. > > hij1nx wrote: > >> You could call Browserify a build tool, but it has a single purpose >> (which is good!), it will bundle your commonjs for use in the browser. >> But a lot of the tools mentioned are more general purpose software >> build tools. >> >> -- >> Paolo Fragomeni >> Co-founder, CTO >> Nodejitsu, Inc. >> www.twitter.com/hij1nx >> www.github.com/hij1nx > -- 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
