By the way there's also Brunch https://github.com/brunch/brunch
--
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
another question, how does onejs figure out which .js files are required?
browserify parses the js, then traverses the ast looking for calls to
require().
On Tue, Apr 24, 2012 at 12:43 PM, Dominic Tarr wrote:
> oh right, that is because you are listing a directory and then requiring
> each item
oh right, that is because you are listing a directory and then requiring
each item automatically.
how does onejs handle that case?
you are right about browserify poluting the global namespace. it should
define it's stuff inside a closure.
On Tue, Apr 24, 2012 at 12:11 PM, Azer Koçulu wrote:
>
On Sun, Apr 22, 2012 at 9:11 PM, Dominic Tarr wrote:
> browserify has _by far_ the most test coverage. I know from my own dabbling
> in the problem that there are _alot_ of edgecases.
I confidently say that OneJS is a well-tested project that faced
_more_ edge-cases already and solved those issue
you'd probably still need a bit on the server side, for validation. you
wouldn't want to give the browser direct access to your database for
example.
On Mon, Apr 23, 2012 at 6:10 PM, Mark Hahn wrote:
> I am thinking of putting the entire app in a client-side browserify
> bundle. I can create th
I am thinking of putting the entire app in a client-side browserify bundle.
I can create the entire BODY element of the dom from js code including the
style info. The idea here is to release an app by just releasing the
bundle.
I could create a generic index.html file that requires the bundle.
Neat. Sounds like I could just use a package.json file for my client-side
files, do an `npm install`, and then a browserify build, which is a nice
workflow.
>
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You rece
> Does browserify let you install npm modules, similar to `ender build package names>, or do you have to manually download them?
You install modules with npm, and require them in your browser's
index.js . Then you do a browserify build against that index.js and it
bundles the deps automatically.
Does browserify let you install npm modules, similar to `ender build , or do you have to manually download them?
--
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 t
browserify has _by far_ the most test coverage. I know from my own dabbling
in the problem that there are _alot_ of edgecases.
https://github.com/substack/node-browserify/tree/master/test
I just use browserify now
On Mon, Apr 23, 2012 at 6:07 AM, Mark Hahn wrote:
> > OneJS moves the revolutio
> OneJS moves the revolution of NPM one step forward and makes it
available for client-side projects!
Does this mean you can load a module directly from the npm registry into
the client to run? Can you also query the registry?
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://g
Ender targets front-end projects. Tools like OneJS
(http://github.com/azer/onejs) and Browserify let you follow the
CommonJS way and code your web projects as CommonJS packages. OneJS is
the tool I maintain and I highly recommend it. It produces
unobtrusive, well structured code and lets you use al
I am new to both ender vs. browserify. Can someone summarize their
differences, advantages, etc?
--
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
Group
13 matches
Mail list logo
