import-js/eslint-plugin-import

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

Open

#1,575 opened on Dec 19, 2019

View on GitHub
 (0 comments) (1 reaction) (0 assignees)JavaScript (1,540 forks)batch import
bughelp wanted

Repository metrics

Stars
 (4,946 stars)
PR merge metrics
 (Avg merge 138d 22h) (3 merged PRs in 30d)

Description

First of all, thanks for this plugin! It's great!

We're using the backtick option with the quotes rule in our codebase. About a week ago, we realized that our linter wasn't catching bad imports. After scratching our heads for a bit, we realized that import/no-unresolved doesn't check require statements that use backticks.

// 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