azat-co / expressjsguide

Express.js Guide code examples

Express.js Guide

Express.js API reference, quick start guide and hands-on tutorials aplenty. 270+ pages, 60+ illustrations, 20+ examples.

http://expressjsguide.com/

Feedback

Any bugs? Submit GitHub issue to https://github.com/azat-co/expressjsguide/issues.

Changelog

November 3, 2013

• Converted to path.join() for consistency (thanks to Peter deHaan)
• Fixed JSHint warnings (thanks to Peter deHaan)
• Added Grunt file (thanks to Peter deHaan)
• Wrong query string definition (thanks to Gary Ryan)
• Errata: typos and grammar

Details: https://github.com/azat-co/expressjsguide/issues?page=1&state=closed

expressjsguide's Issues

Confused by mention of "up-time" module

PDF p23; I was confused by "up-time" module. If I go to the GitHub repo/npm, the package seems to have a "This project is deprecated" message.

Clicking through the article makes it worse as it seems that the "up" module name was recycled into something completely different.

Callback Array Example Issue

In the book, Chapter 15, Page 53 - This code :

var authAdmin = function(req,res,next){ ...

}

var getUsers = function(req,res,next){ 
    ...
    return next();

    return next(); 
}

var renderUsers = function(req,res){

}

var admin = [ authAdmin, getUsers, renderUsers ];

app.get('/admin', authAdmin, getUsers, renderUsers);

should actually be :

var authAdmin = function(req,res,next){ ...

}

var getUsers = function(req,res,next){ 
    ...
    return next();

    return next(); 
}

var renderUsers = function(req,res){

}

var admin = [ authAdmin, getUsers, renderUsers ];

app.get('/admin', admin);

I'd do a pull request, but I can't find that in the actual code. I think it's just a snippet from the book.

Extra )

I would also let you know that there's a typo in the code at page 50 and 52 (I'm talking about the pdf version), when you pass multiple middleware functions at the same route

app.get('/api/v1/stories/:id',function(req,res,next) {
// ...
}), <- the round bracket should not close here
// ...
});

Hope this helps, keep up the good work :-)

doctype

This is to report that your jade template on page 27 of your Express guide should not declare doctype 5 anymore but doctype html.

As doctype 5 was set deprecated - see expressjs/express#1931

Section 17.8 typo - "reg.get()" and "Content-type"

1. "reg.get()" should be "req.get"
2. "app.get('Content-type') should be "app.get('content-type')"

Section 17.7 typo - cookierParser

The string:

express.cookierParser('some secret string')

should be:

express.cookieParser('some secret string')

Section 12.2 (page 39)

app.use(express.logger()); //vanilla logger 
app.use(express.logger('short'));
app.use(express.logger('dev')

missed round bracket

Typo in chapter 10 on page 157

On the lower half of the page, there is the following snippet of code:

module.exports = {
  stories: require('./stories'),
  users: require('./users)
};

It is missing a closing apostrophe for the argument of the second call to require.

These short snippets are not in Github for pull requests, right?

Section 21, Extraneous full stops

var stories = require.('./route/stories');
var users = require.('./route/users');

Should be:
var stories = require('./route/stories');
var users = require('./route/users');

Section 17.1 contains small error

"Query string everything to the left of the question mark"
This should be everything to the right of the question mark.

typos

on page 28

• 1 app.disable('etag');
• 2 console.log(app.disabled('etab'));

The latter should read ‘etag’ most probably...

on page 29

view engine holds the template file extension, e.g., ‘ext’ or ‘jade’, to utilize if the file extension is not passed to the res.render() function inside of the request handler.

here ‘ext’ should read ‘ejs’ I suppose...

Just let me know if such corrections are just creepy or useful to you...

NPM should be npm (global)

per http://npmjs.org/doc/misc/npm-faq.html#Is-it-npm-or-NPM-or-Npm

npm should never be capitalized unless it is being displayed in a location that is customarily all-caps (such as the title of man pages.)