Neither Javascript nor Typescript require semicolon, it is entirely a stylistic choice except in very rare circumstances that do not come up in normal code.

[–] Lemminary@lemmy.world 9 points 18 hours ago* (last edited 18 hours ago) (2 children)

Explanation for nerds

The reason is the JS compiler removes whitespace and introduces semicolons only "where necessary".

So writing

function myFn() {
  return true;
}

Is not the same as

function myFn() {
  return 
    true;
}

Because the compiler will see that and make it:

function myFn() { return; true; }

You big ol' nerd. Tee-hee.

[–] Ephera@lemmy.ml 7 points 17 hours ago

That's terrifying, especially in JS where no type system will fuck you up for returning nothing when you should've returned a boolean.

[–] exu@feditown.com 3 points 15 hours ago (1 children)

Common JavaScript L

[–] Lemminary@lemmy.world 1 points 12 hours ago

Not wrong, but funnily enough, it's a linting rule win. I'd go nuts if I didn't have my type checks and my linters. My current L, though, is setting up the projects initially and dealing with the configuration files if I raw dog it, but that's a problem with ESLint configs and the ecosystem as a whole having to deal with those headaches. So in the end, the JS devs got clever and shifted the blame to the tooling. 😅

[–] Maiq@lemy.lol 3 points 18 hours ago (1 children)

That's good to know. Don't know how I didn't know this. Been writing JS since 2000. Always just used them I guess. Ecmascripts look funny to me without them

[–] Lemminary@lemmy.world 3 points 18 hours ago

Same here. My brain interprets them as one long run-on sentence and throws a parsing error.

[–] Ephera@lemmy.ml 2 points 17 hours ago

Hmm, a webdev colleague said he'd normally prefer without semicolons, but used them anyways for better compile errors.