Semicolon before IIFE should be mandatory

[MatthewCochrane]

The following code produces a rather cryptic javascript error when run

console.log("hello world")
(function () {
  // Extra logic goes here. (see below)
})()

Here's the console output you get when you run it: (try running it in your browser now (ctrl-shift-j))

VM46685:1 hello world
VM46685:2 Uncaught TypeError: console.log(...) is not a function
    at <anonymous>:2:1
(anonymous) @ VM46685:2

Eslint does not give any warnings or errors. The standard mode forces us to omit semicolons, so I propose that a rule to help avoid this case should be added to the standard. Those with more experience than me can probably better suggest an implementation.

A starting point could be:

any line starting with a ( character should require a ; before it

[CiQL]

There already exists a rule for this:

Never start a line with (, [, or `. This is the only gotcha with omitting semicolons, and standard protects you from this potential issue.
eslint: no-unexpected-multiline

I don't know why it doesn't give you any warnings or errors, though.

[lukehutton]

I don't get any errors when have code like this in separate js file, shouldn't there be error for no-unexpected-multiline ?

// ✗ avoid
(function () {
  window.alert('ok')
}())

[feross]

@mattisback What version of standard are you using?

Using standard@11.0.1 I get an error with your example:

/Users/feross/code/standard/t.js:2:1: Unexpected newline between function and ( of function call.

I think you're likely using an old version of standard.

[feross]

@lukehutton You're referring to a separate issue. See #786

[no-response]

This issue has been automatically closed because there was no response to a request for more information from the issue opener. Please leave a comment or open a new issue if you have additional information related to this issue.