Automatic Semicolon Insertion ASI in JavaScript Explained

Automatic Semicolon Insertion, or ASI, is the JavaScript parsing behavior that lets many statements omit written semicolons. It is defined by the ECMAScript specification and matters because it changes how the parser separates statements before your code runs.

ASI is predictable, but it is not a general "fix my code" feature. It only inserts semicolons in specific situations.

The goal is to know when ASI helps and when a missing semicolon can make the next line attach to the previous expression.

That matters because ASI can make clean-looking code run correctly, but it can also leave valid code with a meaning you did not intend.

The Basic Idea

Most of the time, ASI handles ordinary line breaks between statements. The next example has no written semicolons, but each line is still a separate statement.

javascript

const x = 5
const y = 10
console.log(x + y)

Into code that behaves like separate statements. The result is 15.

The important detail is that ASI works while parsing source text. It is not a runtime feature and it does not change values after the program starts.

When ASI Inserts a Semicolon

In beginner terms, ASI can insert a semicolon when the parser reaches a place where the code cannot continue without one.

Common cases include:

• A line break where the next token cannot continue the current statement
• The end of the input
• Before a closing brace in certain statement lists
• Before a restricted token after a forbidden line break

The exact specification wording is more formal, but the practical habit is simple: ASI helps when the parser needs a separator and inserting one is allowed.

Restricted Productions

Some JavaScript syntax has a "no line break here" rule. If you put a line break there, ASI inserts a semicolon.

The most common beginner case is return:

javascript

function getAnswer() {
  return
    42
}

This returns undefined, not 42. ASI inserts a semicolon right after return.

Write the value on the same line. That keeps the return value attached to the return statement instead of becoming unreachable code on the next line.

javascript

function getAnswer() {
  return 42
}

This rule also matters for throw, break, continue, yield, and postfix increment or decrement.

When ASI Does Not Help

ASI does not insert a semicolon if the next line can legally continue the previous expression. That is where surprises happen.

javascript

const items = [1, 2, 3]
[0].toString()

The second line can be read as property access on the first array expression, so ASI does not separate the statements.

A leading semicolon protects the new statement:

javascript

const items = [1, 2, 3]
;[0].toString()

The same kind of risk can happen with lines that begin with a parenthesis, slash, plus, minus, or template literal. The exact result depends on the expression before it.

ASI Is About Parsing, Not Style

ASI explains why both semicolon and no-semicolon styles can work. It does not decide which style your project should use.

If your team writes semicolons, keep writing them. If your team omits semicolons, use a formatter and learn the continuation cases.

Practical Rule

If a line starts with syntax that could continue the previous expression, be careful. Add a semicolon before that line or write the previous statement with an explicit semicolon.

For broader formatting choices, read the JavaScript code style guide. You can also try these examples in Chrome DevTools.