The latest articles on DEV Community by Sumit Kumar Surana (@ssurana2). https://dev.to/ssurana2 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F693651%2Fe4c697c3-643d-4144-a14c-1a337207d9ec.jpeg https://dev.to/ssurana2 en Sumit Kumar Surana Sun, 23 Jan 2022 17:20:40 +0000 https://dev.to/ssurana2/semicolon-or-no-semicolon-2d7h https://dev.to/ssurana2/semicolon-or-no-semicolon-2d7h <p>I have 10 years of experience being a JavaScript developer and I forget that semicolon is optional. Adding a semicolon in the end is a simple instinct for me.</p> <p>From my point of view, if you are using the right tools like jshint or jslint to catch the syntax errors before pushing the code to your repository, it doesn't matter if you use a semicolon or not. </p> <p>I use semicolons in the end because I am tuned that way while working with professionals or mentors who end the statement with a semicolon. I also advocate using semicolons in the end because of the following reasons.</p> <h3> Automatic semicolon assertion </h3> <p>I won’t spend too much time explaining about it since it is really well articulated in ecma specs <a href="https://tc39.es/ecma262/#sec-automatic-semicolon-insertion">https://tc39.es/ecma262/#sec-automatic-semicolon-insertion</a>.</p> <p>To put it simply, it is better to handle the semicolon ourselves than relying on a compiler/minifier which has a chance of being unpredictable. Especially, when you are using ‘[‘ or ‘(‘ or binary operator or a regex in the next line without ending the previous statement with a semicolon. Refer <a href="https://tc39.es/ecma262/#sec-asi-interesting-cases-in-statement-lists">https://tc39.es/ecma262/#sec-asi-interesting-cases-in-statement-lists</a>.</p> <p>I prefer lesser risk on my production code and I believe in the statement that if something can go wrong it will definitely go wrong.</p> <h3> Consistency </h3> <p>Most developers nowadays are full stack developers who have dabbled in one or more backend languages. And most of the popular backend languages (apart from <a href="https://www.python.org">python</a> that I know of) have statements ending with semicolon. </p> <p>So when a developer tends to switch between other programming languages and JavaScript they don't have to unlearn the idea of not putting the semicolon in the end. Remember it is optional. So no offense if someone puts it or omits it. But the idea is to keep a single standard and consistency so that it doesn't cause any confusion among team members on what to follow. So make sure you choose one or else brace yourself for resolving lots of ideology clashes among the team members like the discussion going on at <a href="https://davidwalsh.name/javascript-semicolons">https://davidwalsh.name/javascript-semicolons</a>.</p> javascript webdev