News for hackers. Stuff that matters.
Re:The Great CoffeeScript to Typescript Migration of 2017 by feross on Saturday May 16, 2020 @02:44AM (#23201031)
The behavior of ASI is fully specified. Semicolons are optional. There is no undefined behavior in the language spec that makes using semicolons somehow safer.

Furthermore, even if you always write semicolons you are still subject to ASI modifying your code by inserting additional semicolons where you don’t want them. So you need to learn the rules of ASI regardless of whether you use semicolons or not. https://feross.org/never-use-semicolons/

Re:The Great CoffeeScript to Typescript Migration of 2017 by CuriousSkeptic on Saturday May 16, 2020 @08:28AM (#23202853)
There is no ASI in “strict mode”. And modules are always in strict mode.

Edit: I was mistaken about strict mode.

Re:The Great CoffeeScript to Typescript Migration of 2017 by pygy_ on Saturday May 16, 2020 @08:37AM (#23202903)
That is just not true. You can write semi-less JS modules, strict mode and ASI are orthogonal.
Re:The Great CoffeeScript to Typescript Migration of 2017 by CuriousSkeptic on Saturday May 16, 2020 @10:23AM (#23203595)
Indeed, just read the spec: https://tc39.es/ecma262/#sec-automatic-semicolon-insertion

No mention of strict mode in the section of ASI. Could have sworn that the ASI issues I’ve ran into in the past was resolved by using strict mode, not sure what I’ve got that from.

Re:The Great CoffeeScript to Typescript Migration of 2017 by searchableguy on Saturday May 16, 2020 @04:20AM (#23201471)
Thanks for the link!