Errata

"Avoiding eval()" is shown as a subsection of "Avoiding Implied Typecasting" both in the table of contents and on page 21. Notice that those sections have different title font sizes.

Note from the Author or Editor:
Correct, "Avoiding eval()" should be the same heading level as the headings before and after

The book states: "there is no way to define constants in JavaScript".

We actually can create constants using the const keyword:
const foo = 42;

Note from the Author or Editor:
well, not standartized yet

Change

there is no way to define constants in JavaScript (although...)

to

there is no standard way to define constants in JavaScript yet (although.... and, additionally, a `const` is expected in ECMAScript 6)

Claims that a con is: "Property names cannot be minified."

Note that property names can be minified using the Advanced mode of the Closure Compiler.

Note from the Author or Editor:
Change

Property names cannot be minified

to

Property names cannot always be safely minified, especially by simpler minifiers

sayHi.apply(alien, ["humans"]);

This is not valid because sayHi is not in scope.
The following will work:
alien.sayHi.apply(alien, ["humans"]);

Note from the Author or Editor:
yeah, it's in scope only if it's considered continuation of the previous example. But there's no value in that, so it should be fixed.

sayHi.apply(alien, ["humans"]); // "Hello, humans!"

should become

alien.sayHi.apply(alien, ["humans"]); // "Hello, humans!"

As already pointed out by Ren Vermeulen on p.79, sayHi.apply/sayHi.call should be alien.sayHi. It's not that the code doesn't work as you say (because it does), but it's misleading because you're trying to demonstrate that:

alien.sayHi('world');

is the same as:

alien.sayHi.apply(alien, ['world']);

which only happens to behave the same as:

sayHi.apply(alien, ['world']);

because you have defined sayHi in exactly the same way in both examples, neither of which reference `this`.

"Advanced minification tools such as...Google Closure compiler will rename local variables...but never global variables, because it's not safe to do so."

This is not true of the Closure Compiler -- in Advanced mode, it has this capability. Admittedly, it is not safe for arbitrary JS, but it is if you follow the caveats for Advanced mode:

http://code.google.com/closure/compiler/docs/api-tutorial3.html

Note from the Author or Editor:
Make the last bullet (where ` and ` denotes code formatting):

Smaller code after minification?most minification tools will rename local variables (so `event` will likely become just one character such as A) but willl not rename global variables, because it?s usually not safe to do so. (Google Closure compiler in "advanced" mode is an exception, but even then you have to be careful.)

for (i = 0; i < max; i += 1) {
name = this.decorators_list[i];
price = Sale.decorators[name].getPrice(price);
}

if the sale decorated by mutiple decorators,i'm afraid of these code can't get the correct price result

Note from the Author or Editor:
Works as advertised when it comes to the decorators part. However there's a mistake in the constructor where the `price` initializes to `true`, which is later converted to 1 so the final decorated price is almost certainly off, unless you work with $1 :)

So on page 154 change

this.price = (price > 0) || 100;

to

this.price = price || 100;

like in the previous example on page 152