[nodejs] Best practices for sharing code and data between the server and client

2012-05-30 Thread Amjad
Hello everybody! I'm new to the great world of Node.js and have been playing around with different modules and frameworks. However, there seems a lot of methods for sharing server code with the client, and there are no default way for doing that. I have come across many ideas: express-expose: th

Re: [nodejs] Best practices for sharing code and data between the server and client

2012-08-13 Thread Mariusz Nowak
See also https://github.com/medikoo/modules-webmake the idea is to use same module "format" on server and client side, so you can easily share same code on both sides. I use it with success. Currently I work with application for which client-side code is built of over 200 Node.js style modules a

Re: [nodejs] Best practices for sharing code and data between the server and client

2012-08-13 Thread Jeff Barczewski
Mariusz, After reviewing your readme, webmake looks pretty nice! One idea, if you made your API signature use function (require, exports, module) then it would be compatible with AMD's commonjs signature, and there could be some nice ways to integrate with AMD modules and tools. Just somet

Re: [nodejs] Best practices for sharing code and data between the server and client

2012-08-13 Thread Mariusz Nowak
@Jeff Thanks for that note, I might change that signature in near future just to resemble some standard, however I doubt any external tools can benefit from that, at least I can't imagine any valid use case. On Monday, August 13, 2012 6:25:45 PM UTC+2, Jeff Barczewski wrote: > > Mariusz, > > Aft

Re: [nodejs] Best practices for sharing code and data between the server and client

2012-10-01 Thread Ted Young
> > One problem - was no easy way (or I didn't found it) to browserify also > templates for my backbone.js app. > So I wrote tiny plugin resourcify > (https://github.com/alexeypetrushin/resourcify) that handles > templates (eco, ejs, handlebars, hogan, jade) same way as ordinary js files. > May

Re: [nodejs] Best practices for sharing code and data between the server and client

2012-10-03 Thread Gustavo Machado
Here's a pretty good article about doing it with AMD: http://joseoncode.com/2012/08/30/share-your-server-side-templates-to-the-browser/ Gus On Mon, Oct 1, 2012 at 11:55 PM, Ted Young wrote: > > > > One problem - was no easy way (or I didn't found it) to browserify also > templates for my backbo

Re: [nodejs] Best practices for sharing code and data between the server and client

2012-05-30 Thread Martin Cooper
On Wed, May 30, 2012 at 4:58 AM, Amjad wrote: > Hello everybody! > > I'm new to the great world of Node.js and have been playing around with > different modules and frameworks. However, there seems a lot of methods for > sharing server code with the client, and there are no default way for doing >

Re: [nodejs] Best practices for sharing code and data between the server and client

2012-06-02 Thread Amjad
Thank you very much everybody for your notes! @Martin I tried to have a fast look at YUI. What gives YUI the ability to run client code on the server? I mean what makes it different from other Javascript "MVC" frameworks such as Backbone.js? On Thu, May 31, 2012 at 6:43 AM, Martin Cooper wrote

Re: [nodejs] Best practices for sharing code and data between the server and client

2012-06-02 Thread Martin Cooper
On Sat, Jun 2, 2012 at 6:20 AM, Amjad wrote: > Thank you very much everybody for your notes! > > @Martin > I tried to have a fast look at YUI. What gives YUI the ability to run client > code on the server? I mean what makes it different from other Javascript > "MVC" frameworks such as Backbone.js?

Re: [nodejs] Best practices for sharing code and data between the server and client

2012-06-02 Thread Amjad
Really interesting thank you Martin. On Sat, Jun 2, 2012 at 6:45 PM, Martin Cooper wrote: > On Sat, Jun 2, 2012 at 6:20 AM, Amjad wrote: > > Thank you very much everybody for your notes! > > > > @Martin > > I tried to have a fast look at YUI. What gives YUI the ability to run > client > > code