Atypical CoffeeScript is #4 on npm The guy is specifically targeting single page apps. Backbone is the heavyweight king in that space.
Not sure how npm-www relates? On Monday, March 25, 2013 1:53:18 AM UTC-7, Raynos wrote: > > typical node projects use npm & browserify for frontend. NOT bower. > > typical node projects use JavaScript. NOT coffeescript. > > typical node projects don't have grunt boilerplate. > > Serverside "MVC" is 100% overrated. > > Usage of backbone on the server is unnecessary, usage of it on the client > is completely 100% orthogonal to setting up the "boilerplate" for a typical > node project. > > As for the need for a "boilerplate", one already exists. It's called > https://github.com/isaacs/npm-www > > > On Sun, Mar 24, 2013 at 10:25 PM, Prajwal Manjunath > <[email protected]<javascript:> > > wrote: > >> Hi, >> >> I was trying to build a web app on express, and on the way I couldn't >> help but notice that there was a lack of proper boilerplates encompassing >> all major aspects of modern web apps. Now, a typical node project would use >> Bower for client-side library management, Grunt for dev workflow >> management. I couldn't find a boilerplate using these. >> >> Also, most boilerplates leave the entire configuration in one file >> (index.js/app.js). This is a nightmare for larger apps, and the lack of >> (intuitive) global variable declarations in CoffeeScript compounds the >> issue of splitting them into separate files. >> >> I really felt Node projects need a minimal wrapper around them, much like >> Marionette wraps Backbone to provide what most backbone developers felt >> were necessary of was best practice.* This is just a callout to see if >> anyone else feels the same, and to express interest in a collaborative >> project to achieve this.* >> >> My expectation of such a 'wrapper' would provide the following: >> >> - Effective ready to use templates for common Bower packages and >> Grunt tasks. >> - Use coffeescript everywhere. >> - A decentralized configuration architecture that minimizes content >> in the app entry script(index.js/app.js), and splits config into several >> files based on context. >> - Similar architectures to decentralize routes, and sever side models >> and controllers. >> - A scalable pattern and folder structure for building large >> Backbone/Marionette apps. >> >> And more things as more people offer their inputs. >> >> -- >> -- >> 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]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> >> --- >> You received this message because you are subscribed to the Google Groups >> "nodejs" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- -- 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 --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
