Web Development with Node and Express

Errata for Web Development with Node and Express

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted Date Corrected
PDF
Page IX
United States

Sentence "Just having gotten back from a trip to Lisbon, travel is on my mind, so the exmaple website I have chosen is for a fictional travel company in my home state of Oregon (the Western Meadowlark is the state bird of Oregon)." The word "example" has a couple of letters transposed.

Note from the Author or Editor:
Change "exmaple" to "example".

Tom Bowersox  Mar 25, 2014 
ePub
United Kingdom

In Chapter 5 section: Cross-Page Testing There are a number of minor mistakes with the example which will cause it to fail or not work if followed word for word. 1: views/tours/hood-river.handlebars the href link in <a class= "requestGroupRate" href= "/request-group-rate"> should either be "./request-group-rate" or "tours/request-group-rate", the current example resolves to localhost:3000/request-group-rate which does not match with the routing in meadowlark.js 2: The cross site test for oregon coast tour should not have the referrer as "'http://localhost:3000/tours/hood-river'" as it then won't fail the test, "We’ll see that one of our tests is failing…it failed for the “Oregon Coast Tour” page, which should be no surprise, since we haven’t added that page yet.". It doesn't fail the test, as the test is wrong. Catch22- Who tests the tests!! 3: The command "mocha -u tdd -R spec qa/tests-crosspage.js 2>/dev/null" when run on osx will result in a silent failure, unless the user has added mocha as a global node module using - npm install mocha -g (is this just my setup causing these problems?)

Note from the Author or Editor:
Fixed.

Joseph McLoughlin  Apr 20, 2014 
PDF
Page 16
Last sentence, 'Tip' inset

"You could change the route to be anything you want, and change the file to be anything you want. For example, if you had a different “about” page for each day of the week, you could have files public/about_mon.html, public/about_tue.html, and so on, and provide logic in your routing to serve the appropriate page when the user navigates to http://localhostd:8088/about" http://localhostd:8088/about should be http://localhost:8088/about

Note from the Author or Editor:
Fixed.

Anonymous  May 07, 2014 
PDF
Page 19
Second sentence of second paragraph of 'Scaffolding' section

The second sentence contains 'more a more' : "The advantage of this approach is that it could generate more a more sophisticated framework...".

Note from the Author or Editor:
Delete the first "more" so that it reads "...could generate a more sophisticated framework".

Anonymous  Mar 29, 2014 
PDF
Page 21
2nd 'tip' section

"It will make it easier to sport redirect issues in your code, or incorrect status codes, which are often overlooked. " Type in sport, presumably should be spot.

Note from the Author or Editor:
Fixed.

Anonymous  May 07, 2014 
ePub
Page 70
United Kingdom

In the list item: "lib/request.js Exetnds Node’s http.IncomingMessage object to provide a robust request object. For information about all the request object properties and methods, this is where to look." Extends is misspelt.

Note from the Author or Editor:
Fixed.

Joseph McLoughlin  Apr 20, 2014