Errata

Maintainable JavaScript

Errata for Maintainable JavaScript

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.

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 Page 35
in 2nd paragraph from the bottom

"... for-in loop that iterates over properties for an object."

should be replaced with:

"... for-in loop that iterates over properties of an object."

 Timea Bálint  Nov 23, 2018 
PDF Page 69
"Accidental Globals" 1st paragraph

In

"When you assign a value to variable that ..."

The noun phrase "variable" seems to be missing a determiner before it.

It should be "When you assign a value to a variable that ..."

 Timea Bálint  Aug 10, 2020 
PDF Page 70
Top of this page, 2nd paragraph

In "This way is a lot less error prone than omitting ..." it appears that "error prone" is missing a hyphen. It should be "This way is a lot less error-prone than omitting ..."

 Timea Bálint  Aug 10, 2020 
PDF Page 72
2nd code snippet from the bottom (last statement)

A semicolon is missing at the end of this statement:

ZakasBooks.HighPerformanceJavaScript = {}

It should say:

ZakasBooks.HighPerformanceJavaScript = {};

The omission of the semicolon in this case technically is valid, because ASI will do its "magic", but it felt weird that the previous two statements end with one and only the last statement is missing a semicolon.

 Timea Bálint  Nov 23, 2018 
PDF Page 89
1st paragraph

In

"Another time when when developers typically use null ..."

"when" is used twice in a row. Consider deleting one of them.

 Timea Bálint  Sep 07, 2020 
PDF Page 98
2nd paragraph

In the sentence: "The most likely cause of an error in the previous example is a null reference being passed in to the function."

"in to" should be "into".

 Timea Bálint  Sep 11, 2020 
PDF Page 110
paragraph before last code snippet

In the sentence: "... so the only option for safely adding new functionality is to create an facade."

"an facade" should be "a facade"

 Timea Bálint  Sep 22, 2020 
PDF Page 140
code snippet

There are two instances on this page where the "noempty" option is used incorrectly like this: noempty-true. This should be replaced with: noempty=true

 Timea Bálint  Oct 06, 2020