That's strange. Your commit is correct, but i don't see this bugs under ubuntu & jshint 2.1.19, when run make test

I saw the same errors if I just typed jshint . at the project root. But I see now that my jshint was old (0.9.1). I don't see them with 2.1.9. Weird that it would have changed to tolerate them.

Ah, starting with version 2.0, the "extra comma" error is raised only if the es3 option is not set to true:
http://jslinterrors.com/extra-comma/

And the other error is raised only if the es5 option is not set to true (is it true by default?):
http://jslinterrors.com/expected-an-identifier-and-instead-saw-a-a-reserved-word/

No problems. Your commit is correct. I'd prefer to see such warning for es5. Because old browsers work with es5-shim, that fixes prototypes but does not fixes syntax problems.

Unfortunately turning on es3 in .jshintrc causes it to complain about every occurrence of assert.throws() because throws is a reserved word (but why didn't it complain about that with jshint 0.9.1 when it was complaining about quoteless "null" as a key?). Maybe there's another way to get it to check for the extra commas, but I haven't found it.