Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[X] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:

Tell us about your environment (npx eslint --env-info):

Node version: v24.2.0
npm version: v11.3.0
Local ESLint version: v9.24.0 - v9.29.0
Global ESLint version:
Operating System: darwin 24.5.0

What parser are you using (place an "X" next to just one item)?

[X] Default (Espree)
[ ] @typescript-eslint/parser
[ ] @babel/eslint-parser
[ ] vue-eslint-parser
[ ] @angular-eslint/template-parser
[ ] Other

Please show your full configuration:

export default [
    {
        "rules": {
            "no-array-constructor": [
                "error"
            ]
        }
    }
];

What did you do? Please include the actual source code causing the issue.

let foo
Array(1, 2, 3).forEach(doSomething)

Playground Link

What did you expect to happen?

The autofix for the above code should not introduce a semicolon between the let declaration and the following statement, i.e. the fixed code should look like this:

let foo
[1, 2, 3].forEach(doSomething)

What actually happened? Please include the actual, raw output from ESLint.

The autofixed code includes an additional semicolon:

let foo
;[1, 2, 3].forEach(doSomething)

What changes did you make? (Give an overview)

This pull requests affects autofixes and suggestions provided by no-array-constructor and no-object-constructor. In some cases, mostly related to TypeScript syntax, the rules would previously insert an unnecessary semicolon before the fixed code. The logic to determine if a semicolon is necessary resides in the needsPrecedingSemicolon function in lib/rules/utils/ast-utils.js. This function was updated to handle cases where an expression statement is predeced by:

1. an uninitialized variable declaration
2. TypeScript syntax that does not require a following semicolon

This change affects autofixes and suggestions provided by no-array-constructor and no-object-constructor.

These are some examples of code where the mentioned rules will no longer add a semicolon before an array or object literal that replaces new Array() or new Object():

/* eslint no-object-constructor: "error" */

var a
new Object()

/* eslint no-array-constructor: "error" */

let foo
new Array(1, 2)

// The next examples require the typescript-eslint parser

type xtring = string
Array()

declare function test(): void
new Array("A", "B")

const bar = Math.sign(Math.random() - .5) as -1 | 0 | 1
new Array(0, 1)

Playground Link

More examples for code that will no longer have a semicolon added before the next statement can be found in the unit tests for no-array-constructor:

Is there anything you'd like reviewers to focus on?