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

描述

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)

貢獻者指南

技術棧

javascriptnodejs

領域

developer experience

議題類型

bug

難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。

2

預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。

1-3 hours

活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。

stale

清晰度議題是否清楚說明預期改動、驗收標準和下一步。

clear

前置要求

ESLint plugin developmentAST traversal

新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。

70

研究方向

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.