ASI Bug introduced during Concatenation

lib.js

// This library file decides to use ASI everywhere

var fn = function () {
    //...
} // semicolon missing at this line

my_app.js

// My site's code, starting with an IIFE

(function () {
    //...
})();

When these two files become concatenated and minified, lib.js introduces a bug in my perfectly-valid my_app.js file because it decided to use ASI.

You need to guard against this regardless—this is a common thing even for libraries that use semicolons everywhere.

The best way to do this, is follow the rules I've laid down in my blog post, specifically If your line starts with ( or [ write a single semicolon before that.

I get that, but what you're essentially saying is that everyone else in the community has to add safety guards to their code because you want to use an error correction component of the language to avoid writing some semicolons. You have to admit that it seems completely ass-backwards.