Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upAllow semicolon at the end of an IIFE #663
Comments
This comment has been minimized.
This comment has been minimized.
qzb
commented
Oct 21, 2016
|
I'm afraid that eslint doesn't support such exception. Currently all you can do is suppressing error raised by semi rule for last line of the file: ;(function () {
// ...
})()
; // eslint-disable-line semi |
This comment has been minimized.
This comment has been minimized.
|
Thanks for the update! At least I have a work around. |
This comment has been minimized.
This comment has been minimized.
|
Thanks for the help @qzb! I found a related issue in eslint: eslint/eslint#6271 Unfortunately it looks like they did not decide to implement this option. Sorry! Closing this for now, but feel free to continue discussion. |
Flet
closed this
Oct 24, 2016
lock
bot
locked as resolved and limited conversation to collaborators
May 10, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
dalelotts commentedOct 19, 2016
Since converting to standard, users of my directives are having problems with concatenating and minifying my directive with other code. The root cause of the problem is that standard does not allow
;at the end of an IIFE.If my directive is concatenated with another file that starts with an IIFE they get a parser error and report defects like the following:
dalelotts/angular-bootstrap-datetimepicker#347
dalelotts/angular-bootstrap-datetimepicker#338
If I could terminate my IIFE with a
;, this would fix the issues they are having.