Middleware in NodeJS

Posted March 16th, 2012 by guidone with No Comments

Talking with a collegue of mine I came up with this solution about organizing the code in NodeJS+Express using middlewares.
Consider this example in which we have a simple page that performs two queries and shows the result in a template.
Since everything is asynchronous, we chain in two queries in this way

app.get('/mypage',function(req,res,next) {
   sequelize.search(query1)
      .on('success',function(res_query1) {
         sequelize.search(query2)
            .on('success',function(res_query2) {
               res.render('my_template',{
                  query1: res_query1,
                  query2: res_query2
                  };
               });
         }
   });

There’s nothing wrong with this, the only problem is that as long as the page gets new functionalities, you keep nesting queries and asyncronous callback.
The resulting code could become unreadable after few cycle of releases.
Continue Reading

JS1K

Posted February 3rd, 2012 by guidone with No Comments

A little amarcord┬áhere: who remembers the “demos”? Those little masterpieces for Amiga competing for the smallest size combined with the most awesome graphical effect?

Well, they’re back, this time using just 1026 bytes of JavaScript and the canvas object. Check this out: http://js1k.com/.

A Javascript manager and build tool

Posted January 31st, 2012 by guidone with No Comments

I was playing around with Jake last days and I came up with an idea for a tool to create a piece of code to handle seamlessly the the various JavaScript libraries in a HTML page with NodeJS and the check/compress/build procedure to release the whole package in production.

I’m still working on the idea, probably it will end up in something with a little bit of conventions for the structure of the files, but these are the key points I really need for this tool:

  • Be able to work with AMD modules and simple JavaScript files at the same time (without converting them to AMD module format)
  • Full support to AMD and module dependencies
  • A unique file to define which JS files and modules to load for each page, used to render the page and build the release package for production (no more manually updating of the build script)
  • Paths mapping for easily switch JavaScript library version (or to point the static resource to a CDN)
  • Check the files against JSHint before building (damn comma in array!)
  • Categories

  • Tags

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2 other subscribers

  • Twitter

    Flickr Stream