The errata list is a list of errors and their corrections that were found after the product was released.
The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.
Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update
| Version |
Location |
Description |
Submitted by |
Date submitted |
| PDF, Mobi |
Page 5
Last Paragraph |
Under the heading: Model-view-"whatever-you-want-to-call-it?
The sentence reads:
"We software architects were already employing a similar, if more abstract approach with ."
There appears to be a missing word.
On the next page, the first full sentence reads:
"One of the more popular patterns to come out of this movement was the , which describes:"
Again a word appears to have been omitted.
|
Brandon Blaylock |
Jul 25, 2014 |
| PDF |
Page 28
1 paragraph |
The last paragraph of the "Compass" section reads
"Because we already installed Node.js and NPM, we can issue the following command
... "
However, there is no command given.
|
Craig |
Dec 16, 2014 |
| Printed |
Page 39
8/10 |
1) you need to change to the git directory before entering the command "grunt serve". (Otherwise, no grunt-file can be found).
2) web application not running with the steps explained.
3) Small typo: read *mkdir* instead of -mkidr-
|
Jean Fontaine |
May 16, 2015 |
| ePub |
Page 75
3rd paragraph |
The paragraph reads as follows:
"Let’s now explore the filesystem to better understand what was created for us (Figure 3-2). Notice the three top-level directories: app, node_modules, and test. The app directory contains all of your application files, node_modules contains your application dependencies, and test contains your test files and the configuration files, such as .bowerrc, .gitignore, .jshintrc, Gruntfile.js, and package.json."
Running the "yo" command myself, it appears the current version places these configuration files in the project root, not in the test folder. I'm not sure if this was an original mistake, or if the behavior has changed since publishing, but I wanted to provide a heads up.
|
Aron Beal |
Dec 07, 2014 |
| PDF |
Page 87
3rd paragraph |
At the beginning of the 3rd paragraph it is stated that two action references were added however both the code sample above the paragraph and the code on the Github project only show the single action on the search button.
|
Chris McCuller |
Jun 16, 2014 |
| PDF |
Page 92
artists for loop, songs for loop |
The namespace for the objects being created and pushed into the artist/song arrays is incorrect.
For both the artist and song for loops the code samples show array.push(App.<object>). It should be array,push(RocknrollcallYeoman.<object>)
|
Chris McCuller |
Jun 16, 2014 |
| PDF |
Page 94
<url> variable definition in SongRoute model method |
It appears that the author's EchoNest API Key is included in the URL:
http://developer.echonest.com/api/v4/song/profile?api_key=HQKUQMIPY2RSRUSV2
&format=json&bucket=audio_summary&bucket=song_hotttnesss&bucket=tracks&bucket=song_type
&bucket=id:7digital-US
|
Chris McCuller |
Jun 16, 2014 |
| ePub |
Page 841
United Kingdom |
Yeoman attempt to run ember generator failed for me on Debian.
The issue was with gifsicle -- once I'd installed gifsicle with apt, it all seemed to work okay. So far, anyway. :)
Oh, and the page number is a location number, as I'm reading the book in the Amazon Cloud Reader.
|
Doug Livesey |
Oct 10, 2014 |