automatic-semicolon-insertion

Closed . This question needs to be more focused. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it focuses on one problem only by editing this post . Closed 8 months ago . I'm writing a JavaScript preprocessor which automatically inserts semicolons in places where it's necessary. Don't ask why. Now I know that the general way to tackle this problem is to write a JavaScript parser and add semicolons where necessary according to the rules in the specs. However I don't want to do so for the following reasons: I don't want to write a full

This question already has an answer here: What are the rules for JavaScript's automatic semicolon insertion (ASI)? 5 answers I've also heard that Go insert them too, but they followed a different approach How does Javascript insert semicolons while interpreting? One of the biggest things I've found is, let's say you have a function that returns coordinates (or any object really), similar to this. function getCoordinates() { return { x: 10, y: 10 }; } You would expect to get back an object right? WRONG! You get back undefined. The interpreter converts the code into this function getCoordinates(

This question already has an answer here: What are the rules for JavaScript's automatic semicolon insertion (ASI)? 5 answers As you might know, ECMAscript tries to be smart and will automatically insert semicolons if you didn't write those explicitly. Simple example function foo() { var bar = 5 return bar } will still work as expected. But there are some caveats if you rely on that. If we re-write that function like so function foo() { var bar = 5 return { bar: bar } } ..that function would now return undefined because the interpreter would insert that semicolon right after the return