`import/no-unresolved` ignores require statements with backticks

Description

// index.js
// Assume a, b, and c do not exist

// Does not result in a linting error
const sweetPotato = require(`a`);

// Shows linting error
const biscuit = require("b");

// Shows linting error
import babyYoda from "c";

Contributor guide

Tech stack

javascriptnodejs

Domain

tooling

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.

fresh

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

clear

Prerequisites

JavaScriptESLint plugin development

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

60

Research direction

Investigate the `import/no unresolved` rule in the eslint plugin import repository. The issue is that the rule does not detect unresolved imports when using backtick template literals in require statements (e.g., require(`a`)). You should look at the rule's source code in `src/rules/no unresolved.js` and the resolver logic for handling `CallExpression` nodes (specifically `require` calls). The fix likely involves adding support for `TemplateLiteral` arguments in addition to `Literal` arguments. Check if there are any existing tests for template literal imports in the test directory.