Except that 'punctuation' in JavaScript comes in the form of a line break, and adding a semicolon is like adding two periods to the end of every sentence just in case someone missed the first one.
This sort of writing generally leaves off periods on the ends of sentences
sometimes, it even leaves off the capitalization at the beginning, as well
and yet it manages to be entirely readable and generally unambiguous
This is remarkably similar to js's automatic semicolon insertion:
if the sentence makes more sense with a period at the end of the line
then the reader usually inserts one automatically, without thinking about it
JS will add the semicolons. If you're using Babel and the rest you most likely are not going to run into all the weird things to do with semi-colons as long as you follow K&R C style for control statements.
But if you want it to, go ahead. What matters, in the end, is consistency to make it look pretty. The more it looks like a single very smart person wrote it the better.
JS is not a language like Ruby or Python.
If someone doesn't like typing semicolons why don't they set up their editor so that it would insert them automatically?
Seems like a silly conclusion