Prerequisites checklist

• I have read the contributing guidelines.

AI acknowledgment

• I did not use AI to generate this PR.
• (If the above is not checked) I have reviewed the AI-generated content before submitting.

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: 22.14.0
• npm version: 10.9.2
• Local ESLint version: 10.2.1
• Global ESLint version: no
• Operating System: windows

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 [{}];

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

/* eslint no-useless-constructor: 2 */

class A {
    foo = 'bar'
    constructor() {}
    *baz() {}
}

What did you expect to happen?

The no-useless-constructor rule to report the constructor as useless and provide a valid suggestion to remove it.

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

The no-useless-constructor rule reports the constructor as useless and provides suggestion to remove it. However, applying the suggestion causes a parsing error:

/*eslint no-useless-constructor: 2 */

class A {
    foo = 'bar'
    
    *baz() {}
}

Parsing error: Unexpected token {

Playground link

The suggestion should insert a semicolon to prevent continuation.

What changes did you make? (Give an overview)

• Updated the no-useless-constructor rule to use a new helper astUtils.canContinueExpressionInClassBody(token) that checks for the following tokens that can cause continuation: [, *, in, instanceof.
• Updated the require-await rule in the same way.
• Also updated astUtils.needsPrecedingSemicolon to avoid unnecessary semicolons in case of uninitialized class fields.

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