import-js/eslint-plugin-import

import/named doesn't work when the target has no exports

Open

#1,147 opened on Jul 30, 2018

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,549 forks)batch import
help wanted

Repository metrics

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

Description

Given:

// a.js
console.log('This file has no exports')

// b.js
import { doesntExist } from './a'

I'd expect the import/named rule to show an error for doesntExist. It doesn't. What am I missing? Is there a way to check for this type of error?

Contributor guide

Research direction
Investigate the `import/named` rule logic to see how it handles modules without exports. Look at the resolver or module parsing code to understand why no error is reported for imported names when the source file has no exports.
Tech stack
javascript
Domain
developer experiencetooling
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptESLint
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70