It's a topic that could seem trivial at first sight, but it actually causes some controversy among JavaScript developers. Semicolons, yes or no?
T...
For further actions, you may consider blocking this person and/or reporting abuse
There's a worse issue with omitting semicolons; consider the following code:
This will throw a TypeError that undefined is not a function, because the brackets around the second IEFE are interpreted as a function call. A semicolon between these lines will solve the issue.
mmh.... what is an IEFE?
Immediately executed function expression.
aha, I've only encountered IIFE so far...
(immediately invoked function expression)
I think we mean the same thing
Greeting from the UK.
I do not see this question much these days but it was a common topic of discussion a few years ago. It was a similar "hot topic" to indent using tabs or spaces.
I have tried developing using both styles and (if you know what you are doing) both styles can work. However, I personally find using semicolons more natural and consistent with code I write in other programming languages.
In all the professional grade code I have reviewed over the last four-five years, using semicolons was the preferred style.
I don't add semicolons while programming, rather I wait till I'm done, hit save and let Prettier add them in for me.
I mostly keep the semicolons in the saved files, since I don't want the built code to have any issues with immediately invoked functions in Javascript.
I don't mean to provide a weak answer, but to me, consistency is more important (and this can be achieved by automatic code formatting).
Not a weak answer. Consistency is the most important thing for linting-related issues. Both standards are completely valid. The only thing I would consider is the team's background and preference.
5 years ago I also feel semicolon boring. But now I use as sign to myself: I finished the working and thinking this line of code.
Yes, I know. It's probably the least bad solution in these cases.
Don't forget dynamic method name
"It's a topic that could seem trivial at first sight"
Also on second and third sight.
I used to use them, and now only do so when necessary