[import/newline-after-import] can't Identify require statement when module name is declared by template string

Description

const assert = require('assert');
const generate = require(`../../src/0118-Pascal's Triangle/generate`);

describe(`#0118-Pascal's Triangle`, () => {});

Expected 1 empty line after require statement not followed by another require.eslint(import/newline-after-import)

Contributor guide

Tech stack

javascriptnodejs

Domain

developer experience

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

ESLint plugin developmentAST traversal

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70

Research direction

The issue reports that the `newline after import` rule fails to recognize a require statement when the module path is a template literal (e.g., `require(`...`)`). The fix involves updating the rule's detection logic in `src/rules/newline after import.js`, likely in a helper function that checks if a node is a `require` call. Currently, the rule might only check for string literals; adding a check for `TemplateLiteral` as the argument of the `CallExpression` with a callee named `require` should resolve the issue. Ensure that the fix also handles cases where the template literal has expressions. No linked pull requests or additional comments provide further direction.