[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.