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 add
pakmanager also inspects requires such as `require('./some/local/module')`
and `require('some-npm-module')`.
It will give you warnings if you have deps listed in package.json which are
not being used as well as if you're requiring files which are neither on
the filesystem nor in package.json.
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.g
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 (s
do any of these do automatic dependency resolving?
On Feb 1, 12:23 am, Phoscur 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
>
Yes, I've seen codesurgeon.
But it doesn't support this:
> -automatic dependency resolving and including files
How do you load all relevant files? Declaring all files explictly would
be a lot of work...
Building a custom require could work by prepending
> function require(module) {
> return r
That is not true. I've been watching that topic, and I couldn't see
anything useful for me in it. Ofc I don't want a build system like Ant.
Who likes XML nowadays??
I've seen cake, but that does not do any of the things I want to be done.
Am 31.01.2012 19:52, schrieb deitch:
> Been a long ongoing
Checkout codesurgeon. https://github.com/hij1nx/codesurgeon
We use this at nodejitsu and for a number of the http://github.com/flatiron
projects.
--
Paolo Fragomeni
Co-founder, CTO
Nodejitsu, Inc.
www.twitter.com/hij1nx
www.github.com/hij1nx
On Jan 31, 1:52 pm, deitch wrote:
> Been a long ongo
Been a long ongoing discussion about this at
http://groups.google.com/group/nodejs/browse_thread/thread/4f5270afb0de400f
On Jan 31, 11:31 am, Phoscur wrote:
> So, this means, there are no other build tools out there?
>
> Am 30.01.2012 17:48, schrieb Phoscur:
>
>
>
>
>
>
>
> > Hi,
> > I've seen so
