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 On Feb 2, 10:42 am, Phoscur <[email protected]> wrote: > Yes, both browserifyand browserbuild assemble a concatenated file with > all files used by require(). > > Eh, just had a closer look at their sourcecode... > browserbuild does not resolve dependencies, it just includes all files > available. > browserify uses some kind of detective to included needed files (so this > is indeed the dependency resolving i ment). > > Am 02.02.2012 06:51, schrieb hij1nx: > > > > > > > > > do any of these do automatic dependency resolving? > > > On Feb 1, 12:23 am, Phoscur <[email protected]> wrote: > >> Great, an alternative to browserify! This is perfect. Now I can choose a > >> build process to combine this with. > >> Thanks a lot! > > >> So far I've seen > >> cake, grunt and codesurgeon for the build process > >> and > >> enderjs, requirejs, pakmanager, browserify and browserbuild to port node > >> modules to the browserside. > > >> This there more? > > >> Am 01.02.2012 03:09, schrieb Nathan Rajlich: > > >>> You can also check out Browserbuild, from > >>> LearnBoost:https://github.com/LearnBoost/browserbuild > >>> On Tue, Jan 31, 2012 at 4:28 PM, AJ ONeal <[email protected] > >>> <mailto:[email protected]>> wrote: > >>> > Your directory structure might look like this: > >>> > - project > >>> > - browser > >>> > - server > >>> Where do you put code, you use on both sides? > >>> You create an npm module for it or you symlink it or you copy it. > >>> I should be possible with just an entry point, say > >>> src/browser.js, to > >>> scan throw the whole source directories bundling all files, > >>> getting > >>> modules it can't find from node_modules/. > >>> you can `require('../server/blah.js')`, but I'd recommend using a > >>> symlink at worst. > >>> I've thought about adding support to list local dependencies in > >>> package.json, but npm doesn't like that last time I checked. > >>> I don't know if Isaac has blessed a solution for that particular > >>> problem or not. > >>> -- > >>> 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] > >>> <mailto:[email protected]> > >>> To unsubscribe from this group, send email to > >>> [email protected] > >>> <mailto:nodejs%[email protected]> > >>> For more options, visit this group at > >>> http://groups.google.com/group/nodejs?hl=en?hl=en > >>> -- > >>> 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 -- 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
