I take back my critique of v2, after examining it in details I'm agreed
that API became better.
Also, my concern was false, actually it's quite easy to add support for
coffee-script and client side templates.
On Saturday, February 23, 2013 4:43:34 AM UTC+4, substack wrote:
browserify v2 was
On April 2, 2013 4:03:23 PM TJ Koury tjko...@gmail.com wrote:
Good advice; I've used dependency injection when building shared backbone
views that need to initialize different client-side libraries.
I'm not a fan of AMD in general; I think the app should be delivered
complete in one request, so
Thanks for replying. I should have been more specific in my question: how
do you get all the correct scripts in the right order and compress
everything into a single request and send it to the client? I don't want
to use require.js or any other AMD since performance is spotty over mobile
Good advice; I've used dependency injection when building shared backbone
views that need to initialize different client-side libraries.
I'm not a fan of AMD in general; I think the app should be delivered
complete in one request, so that over high-bandwidth/high-latency networks
like 3g/4g/lte
I have to say v2 is quite nice! good job
On Feb 22, 5:43 pm, substack subst...@gmail.com wrote:
browserify v2 was just released! browserify lets you write node-style
require() calls for browser code so that you can package up your scripts
and npm modules into a single bundle to serve to
we turned on sourcemaps in development mode the other day, so great!
On Apr 2, 2013, at 9:09PM, tjholowaychuk tjholoway...@gmail.com wrote:
I have to say v2 is quite nice! good job
On Feb 22, 5:43 pm, substack subst...@gmail.com wrote:
browserify v2 was just released! browserify lets you
How do you handle dependencies in purely client-side code?
I use it exactly in the same way it would be used in node.js. From my point
of view it's the point of browserify - environment is exaclty the same in
both browser and server.
File app.js
NavigationView =
Any plans to support custom require in future? It works in node.js - why
make browser version of `requre` different from its original?
On Saturday, February 23, 2013 4:43:34 AM UTC+4, substack wrote:
browserify v2 was just released! browserify lets you write node-style
require() calls for
We are doing some dark magic upcoming
using https://github.com/bmeck/node-module-system +1 if we can get a
standardized require shim. Does not need to be ours.
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You
Question to all concerned who are creating these tools that bundle:
How do you handle dependencies in purely client-side code? I built a
little library that uses transitive reduction along with a manifest file
that lists all known dependencies for each of the browser-side scripts, so
for
Generally I abstract out my implementations and my interfaces. This means a
more verbose code base, but allows me to have the renderer inserted via
dependency injection. It is independent of bundling tech and I have used it
with browserify as well as with AMD to great success. Decoupling those
11 matches
Mail list logo
